chore(spec): align 2025 anchor provenance with release pin - #6
Open
squarepots wants to merge 1 commit into
Open
squarepots wants to merge 1 commit into
squarepots wants to merge 1 commit into
Conversation
squarepots
marked this pull request as ready for review
September 24, 2026 17:23
This was referenced Sep 24, 2026
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
1 participant
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.
Refs #5.
What
Regenerate the 2025 spec anchor provenance header from its configured release pin.
The schema body is unchanged: both the old recorded commit and the configured release pin point to the same
schema/2025-11-25/schema.tsblob.Why
scripts/fetch-spec-types.tsdefaults released 2025 generation to0168c57fc74aba6e6dcf8f0b7191db3caaa5ad65, but the checked-in generated header still records357adac47ab2654b64799f994e6db8d3df4ee19d.A clean regeneration therefore produces a provenance-only diff. This makes the checked-in generated artifact match its configured authority.
Validation
schema.tsblob is identical at both commits.