ci: pin cosign to v2.6.3 (fix release signing)#168
Merged
Conversation
cosign 3.x (pulled by cosign-installer v4.1.2) changed sign-blob bundle handling and fails the release signing step with 'create bundle file: open : no such file or directory'. Pin the cosign binary to the 2.x line so --output-signature / --output-certificate work as the workflow expects. This is the signing behavior that shipped 0.23.0. Signed-off-by: Igor Racic <iracic82@gmail.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.
The 0.24.0 release run failed at the Cosign signing step:
Root cause:
cosign-installerwas bumped 3.9.1 → 4.1.2 (commit ac60005), which pulls cosign 3.x. cosign 3.0 changedsign-blobbundle handling and broke the existing--output-signature/--output-certificateinvocation.v0.23.0signed fine on cosign 2.x.Fix: pin the cosign binary to
v2.6.3(latest 2.x) via the installer'scosign-releaseinput. Keeps the updated, SHA-pinned installer action; restores the proven signing behavior. No publish occurred on the failed run (PyPI/MCP skipped), so re-taggingv0.24.0after this merges will cut the release cleanly.