Skip to content

ci: attest build provenance for release artifacts - #24

Merged
cooper-wright[bot] merged 1 commit into
mainfrom
ci/release-attestation
Sep 18, 2026
Merged

cooper-wright[bot] merged 1 commit into
mainfrom
ci/release-attestation

Conversation

@zackkitzmiller

Copy link
Copy Markdown
Member

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@v3 runs in the release job, after checksum generation and before upload — provenance is only meaningful when generated in the same run that produced the artifacts.
  • Job-level id-token: write / attestations: write instead of widening the workflow-level permissions, so the other jobs keep contents: write only.
  • A post-upload gh attestation verify loop fails the release run if signing is misconfigured, rather than shipping silently.
  • Release notes body and README gained a verification snippet; CLAUDE.md CI descriptions updated.

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).

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.
@cooper-wright
cooper-wright Bot merged commit b1d6f59 into main Sep 18, 2026
1 check passed
@cooper-wright
cooper-wright Bot deleted the ci/release-attestation branch September 18, 2026 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant