docs: pin consumer Proof Gate template to v0.6.0 release SHA - #2
Merged
Merged
Conversation
Replace the all-zero placeholder in examples/runcap-adjudicate.yml with the immutable v0.6.0 release commit (1eb8745). Reword the README and template comments from "replace the all-zero placeholder" to "pinned to Runcap v0.6.0; when intentionally upgrading, replace the SHA with the exact release commit", and keep the explicit rule: never use @v1 or a floating tag for the Proof Gate. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
… pin
Reading a tag ref's `.object.sha` returns the tag object SHA for an
annotated tag, not the commit the Proof Gate must pin. Replace that gh-api
guidance in README and examples/runcap-adjudicate.yml with the full release
commit SHA plus `git rev-parse "vX.Y.Z^{}"` for local peeling, and add a
Tier 3 regression assertion that neither doc reintroduces the unsafe pattern.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This was referenced Jun 28, 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.
What
Post-release documentation-only update. Now that Runcap v0.6.0 is published (npm + GitHub Release, tag
v0.6.0-> commit1eb87456333093c9fb8da6e9c21eef8d850891bc), pin the consumer Proof Gate template to that immutable release commit instead of the all-zero placeholder.Changes
examples/runcap-adjudicate.yml: judgeuses:SHA0000...0000->1eb87456333093c9fb8da6e9c21eef8d850891bc # Runcap v0.6.0; header/inline comments reworded to "pinned to v0.6.0; replace the SHA only when intentionally upgrading"; explicit "never use@v1or a floating tag, use a full immutable commit SHA" rule kept.README.md(Install in a consumer repo): step 3 changed from "Replace the all-zero placeholder" to "The template is pinned to Runcap v0.6.0. When intentionally upgrading, replace the SHA with the exact commit SHA of the release you choose." plus the floating-tag prohibition; the note below now says the template is pinned to the v0.6.0 release commit rather than "intentionally not runnable".Not in this PR
No code or product changes.
npm run check,npm test,npm run test:tier3all pass (the SHA-pinning safety test still passes - the value is a full 40-char immutable commit SHA).Do not auto-merge; awaiting review.