Skip to content

chore(spec): align 2025 anchor provenance with release pin - #2860

Open
squarepots wants to merge 2 commits into
modelcontextprotocol:mainfrom
squarepots:chore/align-2025-spec-anchor-provenance
Open

squarepots wants to merge 2 commits into
modelcontextprotocol:mainfrom
squarepots:chore/align-2025-spec-anchor-provenance

Conversation

@squarepots

Copy link
Copy Markdown

What

Regenerate the 2025 spec anchor provenance header from its configured release pin.

Why

scripts/fetch-spec-types.ts pins released 2025 generation to 0168c57fc74aba6e6dcf8f0b7191db3caaa5ad65, while the checked-in generated header still records 357adac47ab2654b64799f994e6db8d3df4ee19d.

Both commits point to the same schema/2025-11-25/schema.ts Git blob (332c3f0edaf78311e8e9b3a4df4c0785533cbc0e), so this changes provenance only.

The result is that regenerating the released 2025 anchor from its configured default authority no longer produces a spurious header diff.

Validation

  • one generated file changed;
  • only the recorded source commit changed;
  • the upstream schema blob is identical at both commits.

@changeset-bot

changeset-bot Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 3eb4f82

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new

pkg-pr-new Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

@modelcontextprotocol/client

npm i https://pkg.pr.new/@modelcontextprotocol/client@2860

@modelcontextprotocol/codemod

npm i https://pkg.pr.new/@modelcontextprotocol/codemod@2860

@modelcontextprotocol/core

npm i https://pkg.pr.new/@modelcontextprotocol/core@2860

@modelcontextprotocol/server

npm i https://pkg.pr.new/@modelcontextprotocol/server@2860

@modelcontextprotocol/server-legacy

npm i https://pkg.pr.new/@modelcontextprotocol/server-legacy@2860

@modelcontextprotocol/express

npm i https://pkg.pr.new/@modelcontextprotocol/express@2860

@modelcontextprotocol/fastify

npm i https://pkg.pr.new/@modelcontextprotocol/fastify@2860

@modelcontextprotocol/hono

npm i https://pkg.pr.new/@modelcontextprotocol/hono@2860

@modelcontextprotocol/node

npm i https://pkg.pr.new/@modelcontextprotocol/node@2860

commit: 3eb4f82

@claude claude Bot added the v2 Ideas, requests and plans for v2 of the SDK which will incorporate major changes and fixes label Sep 25, 2026
@squarepots
squarepots marked this pull request as ready for review September 30, 2026 15:04
@squarepots
squarepots requested a review from a team as a code owner September 30, 2026 15:04
@squarepots

Copy link
Copy Markdown
Author

@felixweinberger when you get a chance, could you review this one? Same area as #2858. It corrects the source commit in the generated 2025 spec files.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v2 Ideas, requests and plans for v2 of the SDK which will incorporate major changes and fixes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant