ci: publish attestation bundle as release asset on alpha releases - #114
Merged
Conversation
The alpha attest job records provenance in the GitHub attestation store, which external scanners (OSSF Scorecard Signed-Releases) cannot see — the check looks for signature/provenance files among release assets. Upload the Sigstore bundle to the release (attestations.sigstore.json) so the attestation is externally visible.
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.
Scorecard's Signed-Releases check reads release assets, not the GitHub attestation store — our alphas are attested but invisibly. This uploads the Sigstore bundle (
attestations.sigstore.json) as a release asset. Additive; no release flow changes.