ci(release): keyless sign of release artifacts with Cosign #4513
Conversation
This file contains 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
casibbald
approved these changes
Jan 14, 2025
This was referenced Jan 15, 2025
This was referenced Jan 26, 2025
This was referenced Feb 4, 2025
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.
Closes
What changed?
Configure Cosign keyless signing of all release artifacts to the (Goreleaser) release workflow. I am not sure this will work, but there is a fair chance it will. Goreleaser docs: https://goreleaser.com/customization/sign/. I searched the Internet for references, and it seems like Chainguard has done something around this. I just copied https://github.com/chainguard-dev/apko/blob/64e3ae0d1cf09e2e83dd384cd5a4f9c06d48e0a4/.goreleaser.yaml#L34-L39, which should end up like this (Assets; example): https://github.com/chainguard-dev/apko/releases/tag/v0.22.6.
Why was this change made?
Allow our users to verify release artifacts before actually using/installing them.
How was this change implemented?
How did you validate the change?
Release notes
Documentation Changes