Repository navigation
chore(spec): align 2025 anchor provenance with release pin - #2860
squarepots wants to merge 3 commits into
Conversation
|
@modelcontextprotocol/client
@modelcontextprotocol/codemod
@modelcontextprotocol/core
@modelcontextprotocol/server
@modelcontextprotocol/server-legacy
@modelcontextprotocol/express
@modelcontextprotocol/fastify
@modelcontextprotocol/hono
@modelcontextprotocol/node
commit: |
|
@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. |
|
@felixweinberger could you review and merge this when you have a moment? It's a one-line fix in the same area as #2858: the generated 2025 spec header now records the commit that |
What
Regenerate the 2025 spec anchor provenance header from its configured release pin.
Why
scripts/fetch-spec-types.tspins released 2025 generation to0168c57fc74aba6e6dcf8f0b7191db3caaa5ad65, while the checked-in generated header still records357adac47ab2654b64799f994e6db8d3df4ee19d.Both commits point to the same
schema/2025-11-25/schema.tsGit 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