fix: install Cosign v3 from verification bundles - #10
Merged
Conversation
What changed: - pin the bundle-aware official Cosign installer in release and security workflows - add a regression contract and refresh the source manifest Why: - Cosign v3.1.3 no longer publishes the detached signature expected by the old installer
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.
What changed
Root cause
The previously pinned installer expected the legacy
cosign-linux-amd64.sigasset. Cosign v3.1.3 publishes keyless and KMS.sigstore.jsonverification bundles instead, so release run 32205248385 stopped before image signing and publication.Validation
concurrency.queueschema findingNo runtime image code, signing identity, workflow permissions, release ordering, or Cloudflare behavior changes.