OpenAPI 3.2 in 2026: what changed, and why it matters for SSE and AI agents

·1 views

OpenAPI 3.2 is a consolidation release, which is exactly what a contract format needed. The 3.0-to-3.1 jump did the disruptive work — full alignment with JSON Schema draft 2020-12, top-level webhooks, and a sane null model — and 3.2 tightened the edges. If your documents are still 3.0.3, the migration is small in mechanical terms and large in correctness, especially once you start describing streams and feeding specs to code generators and MCP servers. This is a practitioner's summary: what actually changes in your YAML, what breaks in old tooling, and how to document server-sent events proper

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Why You Should Never Trust the Frontend for Server-Side Verification

Earlier today, I was booking a train ticket online. The platform required NIN (National Identification Number) verification before letting me continue. I entered a valid NIN. The verification call failed with a 500 and a generic SOMETHING_WENT_WRONG. Not an invalid-NIN error — an actual server failure.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to organize a large OpenAPI spec: multi-file structure, $ref rules, and CI checks

Every OpenAPI document starts as one clean file. Then it reaches forty operations and the file is 2,000 lines, then a hundred operations and pull requests conflict on every merge, then nobody edits it without a full afternoon of context. The standard advice is "split it with $ref," which is true and unhelpful — split how, along which boundaries, and what breaks in tooling when you do? This is the layout and rule set that survives 200+ operation APIs. Organize by artifact kind first, domain second.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Gev: Gmail label suggestions with an embedded inference engine.

I wanted a simpler way to sort email without sending message text to an AI service. So I started building Gev: a browser extension that reads my Gmail messages and automatically labels them into categories like Receipts, Personal, Updates, or Newsletters. https://github.com/receptron/laya model. The model and ONNX runtime are bundled with the extension. There’s no inference API or hosted model involved and no data is ever sent to an external service or host(except gmail).

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Prepare for Your Final Year Project Viva (Simple Guide)

The viva is where many students lose marks, even with a working project. Examiners usually want to see that you understand what you built. Here is a simple way to prepare. Be ready to explain in two or three sentences: What problem does your project solve? Who will use it?

0 comments Read more at DEV Community