Add build provenance attestation; draft-then-publish for immutable releases - #7
Merged
Merged
Conversation
Two supply-chain/release hardening changes:
1. SLSA build provenance: attest each binary's digest with
actions/attest-build-provenance using the workflow's OIDC identity, so
consumers can prove a binary was built from our sources by this workflow:
gh attestation verify <binary> --repo figma/bazel
The release job gains id-token:write and attestations:write. Only the
binaries are attested, not the .sha256 sidecars.
2. Immutable-releases compatibility: create the release as a --draft with
all assets attached, then `gh release edit --draft=false` to publish.
Immutable releases freeze assets at publish time, so every artifact must
be present while still a draft.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Follow-up to #6 (which got the release pipeline fully green —
8.6.0-figma2published with portable linux binaries). Two hardening changes:1. SLSA build provenance attestation
Adds
actions/attest-build-provenance(v4.1.0, SHA-pinned) in the release job. It signs each binary's digest with the workflow's OIDC identity, binding the artifact to this repo + commit + workflow run. Consumers can then prove a binary was built from our sources (not tampered with or rebuilt elsewhere):id-token: write+attestations: write.dist/bazel-*,dist/bazel_nojdk-*); excludes*.sha256.2. Immutable-releases compatibility (draft → publish)
Immutable releases freeze a release's assets the moment it's published, so all artifacts must be attached before publishing. Changed the release step to:
gh release create "$VERSION" --draft … dist/*(draft, all assets attached)gh release edit "$VERSION" --draft=false(seal/publish)Notes
gh attestation verifyin the workflow header.8.6.0-figma3.04f8fcbe7a— confirm before merging.🤖 Generated with Claude Code