release: attest tarball provenance #146
Merged
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.
This is what I came up with https://github.com/thepwagner-org/actions/blob/main/.github/workflows/golang-release-attest.yaml
Since GitHub packages the attestation tool as an actions step, it can't run as a post-build hook in goreleaser like
cosign ...
could.Luckily GoReleaser leaves the artifacts it generates sitting around in
dist/
, so we can just sign them after the release action has completed!Related