Repository navigation
ci: attest build provenance for release artifacts - #24
Merged
Merged
Conversation
The release job now signs every archive and SHA256SUMS.txt with GitHub build provenance (actions/attest-build-provenance), then verifies the attestations with `gh attestation verify` after upload so a broken signing setup fails the run instead of shipping silently. Provenance is generated in the same run that produced the artifacts, which is what makes the claim meaningful — hence the job-level id-token/attestations permissions rather than widening the workflow defaults. The release body and README document how to verify a download.
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.
Summary
Release archives (and
SHA256SUMS.txt) are now signed with GitHub build provenance, so anyone can confirm a download was built by this repo's release workflow.actions/attest-build-provenance@v3runs in thereleasejob, after checksum generation and before upload — provenance is only meaningful when generated in the same run that produced the artifacts.id-token: write/attestations: writeinstead of widening the workflow-level permissions, so the other jobs keepcontents: writeonly.gh attestation verifyloop fails the release run if signing is misconfigured, rather than shipping silently.Testing
YAML parses and the job graph is unchanged. Attestation can't be exercised locally — the first release run after merge is the real check. Requires GitHub Artifact Attestations to be available for the repo (default for public repos).