Repository navigation
Run release evidence once per commit - #222
Merged
Merged
Conversation
GM12B drops its release-branch push trigger: release branches are only pull-request heads into main, and their pull requests always rerun the proof. Release Evidence groups dispatches by the ref they reproduce, checks out exactly the pushed commit on a push, and cancels only a stale release-branch head. A release tag reuses an earlier successful reproduction of exactly the tagged commit and base, identified by a marker artifact whose producing run must be this workflow, started in this repository by a push of the tagged commit to a release branch; a manual dispatch is never reused, since it runs the code of its ref input. The CI guide gains a release procedure.
jbwinters
enabled auto-merge (squash)
November 9, 2026 01:25
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 process, first part: run release evidence once per commit.
GM12B:
release/**push trigger. Release branches are only pull-request heads intomain, and a pull request from arelease/branch always reruns the proof, so a release head gets one run instead of two. The branch name reaches the scope script only through an environment variable.Release Evidence:
release/**branch cancels the stale head's run; tag and dispatch runs are never cancelled.github.sha), not the branch tip at checkout time.release-evidence-pass-<commit>-<base>.jacquard-core-*tag push reuses an earlier reproduction only whenscripts/release/find-prior-evidence.shfinds an unexpired marker whose run is this workflow, started in this repository by a push of the tagged commit itself to arelease/branch, and successful. A manual dispatch is never reused, because it runs the code of itsrefinput, which the run record does not show. Any API or parse failure falls back to a full reproduction.test/cli/release-evidence-reuse.tpins every acceptance rule with a fakegh.docs/ci-cd.mddocuments the new behaviour and gains a release procedure. Cram transcript files 84 to 85.The workflows cannot run locally; the YAML parses and the script parses under
dash -n. Full local gate: 1246 tests, exit 0.