Repository navigation
release-gate.sh ends the evidence with the line the release criterion reads - #323
Merged
Merged
Conversation
… reads The first v0.4.0 tag run passed every job but `publish the release`, which stopped at release-check: the §30.3 criterion reads the line `just vv` prints when the whole gate passes, and the file the release gate writes from the sharded run carried the run, its jobs and the legs' transcripts, none of which says it. The rehearsals could not show this, since `publish` runs on a tag only. The script now ends the file with `gate: every job of run N passed on <commit>` and `vv: the acceptance gate passed`, the criterion is one function (`repo_model::release::ci_evidence`) with its own test, and RP-18's planted-run test holds the script's output to that function. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013QppGKetUURseXowZun9KY
This was referenced Oct 26, 2026
This was referenced Oct 27, 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
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.
Release-blocking: the first
v0.4.0tag run (40321415513 onaa6593e02) passed every job butpublish the release, which stopped atrelease-checkwithci-evidence: release/vv-evidence.txt does not record the gate passing(#34). The §30.3 criterion reads the linejust vvprints when the whole gate passes; since #320 the file is written from the shardedci.ymlrun and carried the run, its jobs and the legs' transcripts, none of which says it. The six rehearsals could not show this becausepublishruns on a tag only. Nothing was published: no GitHub Release, no crates.io upload; the0.4.0andlatestimage tags were pushed bymanifestand are pushed again by the next run..github/release-gate.shends the file withgate: every job of run N passed on <commit>andvv: the acceptance gate passed, the summary of the run it verified.repo_model::release::ci_evidence, used byrelease-checkand tested on its own (the legs' lines alone are refused; a file naming no commit is refused).conformance_rp_18's planted-run test holds the script's output to that function, so the file the gate job writes is the filerelease-checkaccepts. Two committed-tree plants are in VERIFICATION.md; run by hand onaa6593e02the script names run 40292537147 and ends with the two lines.After the merge: rehearsal 7 on the merge commit, then the tag moves to it (delete
v0.4.0, tag the new commit); commands follow on #34.Generated by Claude Code