Record spec v1.0.0 release in compatibility matrix#115
Merged
Conversation
Keep pins.spec_ref at c636412; normative trees unchanged since pin. Update matrix spec_version label and release run metadata.
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.
Summary
spec_version.versionasv1.0.0after the successfulGitHub Release (run 26698325160).
pins.spec_refandintentproof-tools/SPEC_REFatc636412(noschema/golden/policy diff since the existing pin).
source_refpins unchanged until those repos tag releases.Test plan
npm testbash scripts/check-ecosystem-pins.sh(with sibling checkouts at pinned SHAs in CI)Does not bump tools
SPEC_REF; do that when normative spec content moves.