Conversation
cosign v3 now emits a Sigstore bundle by default; our explicit --output-signature + --output-certificate flags aren't compatible and the empty-bundle-path caused: 'create bundle file: open : no such file or directory'. v2.6.3 keeps the CLI we wrote for. Revisit v3 once we're ready to move to bundle-based attestations. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
v3 changed
sign-blobdefaults to emit a Sigstore bundle; our explicit flags aren't compatible and the empty-bundle-path caused release.yml to fail with:create bundle file: open : no such file or directory. Pinning v2.6.3 which matches the CLI we wrote for. Revisit v3 as a follow-up.