fix(spec): freeze 2026-07-28 release references - #2858
Open
squarepots wants to merge 6 commits into
Open
squarepots wants to merge 6 commits into
squarepots wants to merge 6 commits into
Conversation
|
@modelcontextprotocol/client
@modelcontextprotocol/codemod
@modelcontextprotocol/core
@modelcontextprotocol/server
@modelcontextprotocol/server-legacy
@modelcontextprotocol/express
@modelcontextprotocol/fastify
@modelcontextprotocol/hono
@modelcontextprotocol/node
commit: |
squarepots
marked this pull request as ready for review
September 24, 2026 16:24
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #2857.
What
Finish the 2026-07-28 draft-to-release cutover.
schema/2026-07-28for the generated type anchor, schema twin, and example corpus;SubscriptionsListenResultMetaObjectandSubscriptionsListenResultResponsereference shapes into parity/conformance coverage;schema/draft;Why
2026-07-28 is already released, but the current reference lifecycle still follows the draft schema. The nightly job updates only the generated anchor, while the repository requires the anchor and its derived oracles to stay synchronized.
That leaves a released revision with a moving authority and repeatedly recreates drift between the anchor, schema twin, and fixtures.
Validation
Validated on the fork PR:
check:all;build:alland distribution type smoke test;