Attest release artifacts with build provenance#52
Merged
Conversation
Add actions/attest-build-provenance step to the release workflow so main.js and styles.css are signed via Sigstore and verifiable with `gh attestation verify`. Grants the job id-token: write and attestations: write to support OIDC token minting and recording.
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
actions/attest-build-provenancestep to the release workflow somain.jsandstyles.cssare signed via Sigstore and verifiable withgh attestation verify.id-token: writeandattestations: writefor OIDC token minting and attestation recording.Test plan
1.0.9) and confirm the workflow run shows an "Attest release artifacts" step that succeeds.gh attestation verify main.js -R gtritchie/bulk-propertiesandgh attestation verify styles.css -R gtritchie/bulk-propertiesagainst the published assets.