Pin cosign to 2.x in the release workflow - #49
Merged
Merged
Conversation
cosign 3.x flips the new bundle format on by default, which ignores the --output-signature and --output-certificate flags our signs block passes to sign-blob and then aborts trying to write a bundle to an empty path. The last few releases failed at the signing step for exactly this reason. Pin cosign-installer to v2.6.3 so the release keeps producing the checksums.txt.sig and checksums.txt.pem pair, and so the signing tool stops floating to a latest that can break the pipeline without warning.
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.
cosign 3.x makes the new bundle format the default. That ignores the --output-signature and --output-certificate flags the GoReleaser signs block passes to sign-blob, then aborts trying to write a bundle to an empty path. The v0.3.1 / v0.3.7 / v0.2.3 release runs all failed at this signing step.
Pinning cosign-installer to v2.6.3 restores the checksums.txt.sig + checksums.txt.pem outputs and stops the signing tool from floating to a breaking latest.