ci: configure Cosign keyless release signing#84
Merged
Conversation
Configure keyless cryptographic release signing for all built release archives: - .goreleaser.yaml: Add 'signs' block using cosign to sign the checksums file and generate a '.sigstore.json' Sigstore bundle - release.yml: Add 'Install Cosign' workflow step (sigstore/cosign-installer) so the binary is available during release builds
peczenyj
added a commit
that referenced
this pull request
May 29, 2026
The v3.5.0 pin pointed at 59acb623... which does not exist in sigstore/cosign-installer, so the release workflow failed at job setup (first triggered for v0.7.0, since the Cosign step was added after v0.6.1 in #84). Repin to the real v3.5.0 commit 59acb6260d9c. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
peczenyj
added a commit
that referenced
this pull request
May 29, 2026
The v3.5.0 pin pointed at 59acb623... which does not exist in sigstore/cosign-installer, so the release workflow failed at job setup (first triggered for v0.7.0, since the Cosign step was added after v0.6.1 in #84). Repin to the real v3.5.0 commit 59acb6260d9c. Co-Authored-By: Claude Opus 4.8 <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.
This PR implements Branch 2:
security/release-signingfrom our security-hardening roadmap. It configures keyless cryptographic release signing using Cosign.Changes Implemented:
signsblock to.goreleaser.yamlto runcosign sign-blobonchecksums.txtand generate a Sigstore bundle.sigstore.json.sigstore/cosign-installer(v3.5.0) in.github/workflows/release.ymlso that Cosign is installed and available before GoReleaser runs.This raises our OpenSSF Scorecard rating for the "Signed-Releases" check from
0/10to10/10and ensures that all downstream package managers and users can verify our release archives cryptographic integrity.