Week of November 8 – November 15, 2026
GraphQL Ships Two Specifications in One Week
By Kin Lane · Sent November 16, 2026
This is the fifteenth issue of The Specification Layer.
This newsletter window: November 8 through November 15. Fifty-two specification repositories and twenty-five feeds. Every repository read clean. One feed, the OpenAPI Initiative’s, failed (see Channel Health). 276 pull requests merged. 9 releases cut. 33 posts published.
The core series of forty-six merged 209, 66 by bots (32%), against 232 and 31% last week, and cut 8 releases. 22 of 46 did not move. Reported alongside, not inside: the six added specifications merged 67, 17 by bots, with x402 at 39. Neither release-path dependency, SpecRef or OAI build-infra, merged anything.
Predictions from last week, graded:
| Prediction | Result |
|---|---|
| MCP aligns its website contributing page with the new pull-request policy within two weeks | Right. #3534 merged November 11. The docs had given three different answers on who can open a pull request, and now give one. |
| MCP publishes the transition calendar confirming March 30 by year end | Right. The release-cycle post targets version 2027-03-30. |
| Arazzo 1.2 misses mid-November | Right. The latest release is still 1.1.0. The 1.2 shape question is open (see below). |
| The AI Catalog merges one identifier proposal, not both, before tagging 0.9 | On track. #137 (;kind) was closed without merging, and #138 is open. |
| The AI Catalog tags 0.9 before the end of November | Open. No tag yet. |
| A2A 1.1 is not final by the end of November | Open. Four docs merges. |
The features default is fixed before a 3.3 release candidate |
Open. |
| ORD 1.18 by the end of the year | Open. Two docs merges. |

The Lead: GraphQL Ships Two Specifications in One Week
On November 12 GraphQL tagged its September 2026 edition. The next day the GraphQL over HTTP specification got its first release. The edition merged in #1244, and the announcement says the project now aims for roughly a yearly cadence. The previous edition was a year earlier, and the one before that was four years earlier.
GraphQL over HTTP matters more for the API industry. The GraphQL specification has always been transport-agnostic, so for the decade most GraphQL has run over HTTP, nothing said how. Servers sent application/json and answered 200 even when a request failed, because a 200 was how a client knew the body came from the origin and not from a proxy. The announcement calls it “200 Not OK.” The new specification adds a media type, application/graphql-response+json. A client receiving it knows it can parse the body as a GraphQL response whatever the status code, so servers can finally use status codes properly: 2xx when the request returned data, 4xx or 5xx when it returned only errors.
The edition itself is smaller.
- Empty selection sets are now valid, so the smallest query is
{}. - Directives can carry directives, so a custom directive can finally be deprecated.
- The text on fragments now says what practice was all along: each component declares its own data needs in a fragment, rather than fragments being a tool for removing duplication.
Both documents are tagged releases, not drafts. GraphQL’s repository merged five pull requests all week. Most of the year’s work happened in working groups and in the GraphQL Auxiliary Proposals project.

🎙 AI & Agents, and From the Room
MCP set a release cycle. The announcement moves specification releases to a six-month schedule, following SEP-3398, and targets version 2027-03-30, with 2027-09-28 after it.
- Six months out: Core Maintainer review begins.
- Two and a half months out: soft freeze. Every proposal must be final and merged, which for March puts the soft freeze in mid-January.
- One month out: hard freeze. Only security and release-blocking fixes, and only by full Core Maintainer vote.
The same week, #3529 replaced the individual-sponsor model for proposals with working-group sponsorship. #3534 reconciled the contributing docs with last week’s members-only pull-request policy. #3526 added the Linux Foundation’s stewardship statement under the EU Cyber Resilience Act to the security policy. Nine of MCP’s 22 merges this week came from claude[bot], opened at maintainers’ request, and most of the rest were blog and docs work.
The MCP Registry merged 30, almost all of them service and infrastructure work behind v1.8.9. The one that touches what publishers rely on is a docs clarification: deprecating a server does not remove its latest flag.
The AI Catalog merged its open-objects decision. #131 aligns the specification with ADR-0028: catalog and entry objects are open-ended, so consumers ignore fields they don’t recognize. On the November 12 call, which is recorded publicly through LFX, the group moved from last week’s ;kind toward #138’s shape, urn:air:{publisher}:{name}[:{kind}]. That pull request is still open while the wording is settled. I measured what that grammar does to the 102 catalogs APIs.io harvests in a post on Thursday. In short, 98 publishers use the five-segment form it reads differently. Disclosure: I moved the APIs.io and API Evangelist catalogs to the new form the same day.
A2A merged four docs changes, including a revamp of the specification’s main page. ONNX merged 27. The specification work is operators for opset 29, including pack and unpack for low-bit quantization, plus a clarification that NaN conversion to FLOAT4E2M1 and FLOAT6 is unspecified. The 1.24 milestone is 17 of 57, due December 1. TRACE merged a conformance fix.
In the working groups. At the November 11 Arazzo call, the room leaned toward an explicit step type for 1.2. It would be optional for OpenAPI and AsyncAPI steps, so a 1.1 document stays valid, and required for the new SOAP, RPC and GraphQL steps. Before that can be decided, the RPC and GraphQL proposals need to be seen side by side, and draft #635, opened November 13, does that. No decision has been made. The repository merged three spec clarifications, including steps must contain at least one step and the missing channel value for in.

📐 The Description Layer
OpenAPI took the media-type description back out of 3.2. Last week I reported that #5583 and #5584 added a description field to the Media Type Object on the 3.3 and 3.2 lines. The 3.2 half has been reverted. Issue #5593 says the field shouldn’t go into a patch release. #5594 removes it from the 3.2 text and schema, and #5595 adds a test asserting it is invalid. It stays in 3.3.
There’s a wrinkle worth knowing. The published 3.2 schema at spec.openapis.org does accept description on a Media Type Object, and the 3.2 development branch now rejects it. So a document can pass today’s schema and fail the next 3.2 patch schema. If your tooling validates against whatever 3.2 schema is current, watch for that. v3.3.0 is unchanged at 19 of 40.
Protocol Buffers cut v37.0-rc3, a release candidate, with three breaking changes queued:
- the Java generator now ignores
java_generic_servicesby default; --descriptor_set_innow rejects conflictingFileDescriptorProtoentries;- Python stops accepting JSON booleans in numeric fields.
29 of its 30 merges were the Copybara export bot. gRPC shipped patch releases 1.85.2 and 1.84.3, both hardening channelz. JSON Schema merged three editorial fixes to the development draft. ORD merged two docs changes.
Adoption this week: still no new numbers. Monday’s probe of provider websites failed for the second week running, so the latest counts are still November 2’s. I’d rather say that twice than print deltas that only measure a stale table.

📡 Events, Telemetry and the Data Plane
The OpenTelemetry specification added a Traces Data Model document and configurable SDK component names.
The semantic conventions merged 13:
service.criticalityis promoted to stable;- Linux pressure stall metrics are added;
- an ASP.NET Core metric name is corrected, which is labelled breaking.
OTLP clarified that a profile’s time_unix_nano is its start time. The OpenTelemetry blog announced the deprecation of the Collector batch processor. CloudEvents, OpenMetrics, xDS, xRegistry and the GenAI conventions didn’t move.

🔐 Identity, Policy, Supply Chain
Sigstore is reshaping its next bundle format. On main, #964 decouples the signature from the DSSE payload in the v2 bundle, and #963 removes the public-key hint. It’s development work, not a release. The OCI runtime specification replaced execCPUAffinity with a CPUAffinity process property. OCM made an artifact-reference label part of the specification rather than a convention.
SPDX merged three docs changes on the 3.0 line. SLSA merged nine, all tooling and site fixes. OSV merged eight, mostly dependency bumps. Cedar merged eight, all in its verification and fuzzing code. OpenFeature merged two dependency bumps.

💹 Financial Services Data Standards
x402 merged 39, and one touched the specification: #3707 proposes cards as a network binding for the auth-capture scheme, so a buyer without a funded wallet can pay over x402. It merged as a proposal document under specs/. The Python package shipped 2.28.0.
The Common Domain Model released 7.10.0 and 8.0.0-dev.15, a pre-release, with FX option qualifiers for barrier, digital and Asian options. CALM added its C4 mapping standard 1.0. FDC3’s six merges were infrastructure. The 3.1 candidates milestone is still 0 of 12.

🏛 From the Foundations
The Linux Foundation welcomed Agent Name Service, an open standard for agent identity and discovery built on DNS and the certificates websites already use, with eleven supporting organizations. It joins the AI Catalog, agent cards and the MCP Registry in the discovery layer, and it’s the one that starts from DNS.
At KubeCon North America, CNCF announced new Sandbox projects including Agent Substrate and OpenShell, and the donation of KubeRay. OpenSSF expanded its AI security resources. LF Decentralized Trust took in EUDIPLO, for the EU digital identity wallet deadline, and the Inter-Blockchain Communication protocol.

🤫 The Quiet Ones
Twenty-two of forty-six didn’t move, up from fifteen.
Finished, not dead: CloudEvents, at 1.0.2 since 2022 and still running the event layer, plus xDS, TUF and Notary Project. The OCI image and distribution specifications were quiet this week, which is ordinary for them.
Quiet and worth watching:
- Overlay, with 1.2 closed out and 1.3 at zero of three;
- AsyncAPI, whose 3.0 cleanup milestone is still at 25 of 28;
- the OpenAPI security group, three weeks after its objects moved in from the main specification;
- Agent Skills, quiet since August 9, even as MCP served skills through its extension;
- AGENTS.md, unchanged since September 10.
SPIFFE, the GenAI conventions, OASF, OpenVEX, in-toto Attestation, OpenChain and Moonwalk also didn’t move. Moonwalk last merged in March 2025, and nothing in it suggests an OpenAPI 4.
📡 Channel Health
The OpenAPI Initiative’s feed is gone. Last week openapis.org/feed returned ten items. This week it returns a 404, as do the other usual feed paths. The site appears to have been rebuilt. The blog’s newest post is still July 22, about the new outreach co-chairs. So OpenAPI’s announcements now reach you only through the repository and the mailing list. I’ll find the new feed or record it as unavailable.
How This Was Made
One harvest run against the GitHub REST and GraphQL APIs and twenty-five feeds, November 8 to November 15, 2026. Merged pull requests are counted by merged_at inside the window. A release is a GitHub Release or a new tag. Bot attribution is by author login; machine accounts with ordinary logins count as people.
Where this issue says what a pull request did, I opened it and read its body or its diff.
- GraphQL: I read both changes from the release tags and the GraphQL Foundation’s announcements.
- MCP: I read the release calendar from the merged post.
- OpenAPI: I checked the media-type change against the published 3.2 schema at spec.openapis.org this morning.
- Calls: from calls I attended, I report only what the repositories confirm. The Arazzo step
typeis a direction, and draft #635 is the record of it. MCP working groups aren’t public, so I cover them only from their repositories.
Standing rules: a merge to a development branch is not a published specification. This week that covers OpenAPI 3.2 and 3.3, Sigstore’s v2 bundle, JSON Schema and ONNX’s opset 29. A release candidate is not a release, as with Protocol Buffers 37.0. Milestones are project news.
Predictions on the record:
- MCP’s March release holds its soft freeze in mid-January, and
2027-03-30ships on the date. - Arazzo merges a step
type, optional for OpenAPI and AsyncAPI steps, intov1.2-devbefore the end of the year. - The AI Catalog merges one identifier proposal, not both, before tagging 0.9, and tags 0.9 before the end of November (carried).
- A2A 1.1 is not final by the end of November (carried).
- The
featuresdefault is fixed before a 3.3 release candidate (carried). - ORD 1.18 by the end of the year (carried).
