chore(deps): update module github.com/sigstore/cosign/v2 to v3 #228
Conversation
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
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/github.com-sigstore-cosign-v2-3.x
branch
from
dab1139 to
0bcccdc
Compare
christian-stephen
approved these changes
Oct 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 contains the following updates:
v2.5.2->v3.0.2Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
sigstore/cosign (github.com/sigstore/cosign/v2)
v3.0.2Compare Source
v3.0.2 is a functionally equivalent release to v3.0.0 and v3.0.1, with a fix for CI to publish signed releases in the new bundle format.
--bundleflag specifying an output file to write the Sigstore bundle (which contains all relevant verification material) has moved from optional to required in v3.Changes
v3.0.1Compare Source
v3.0.1 is an equivalent release to v3.0.0, which was never published due to a failure in our CI workflows.
--bundleflag specifying an output file to write the Sigstore bundle (which contains all relevant verification material) has moved from optional to required in v3.Changes
v3.0.0Compare Source
Announcing the next major release of Cosign!
Cosign v3 is a minor change from Cosign v2.6.x, with all of the new capabilities of recent
releases on by default, but will still allow you to disable them if you need the older functionality.
These new features include support for the standardized bundle format (
--new-bundle-fomat), providing rootsof trust for verification and service URLs for signing via one file (
--trusted-root,--signing-config),and container signatures stored as an OCI Image 1.1 referring artifact.
Learn more on our v3 announcement blog post! See
the changelogs for v2.6.0, v2.5.0, and v2.4.0 for more information on recent
changes.
If you have any feedback, please reach out on Slack or file an issue on GitHub.
Changes
v2.6.1Compare Source
Bug Fixes
v2.6.0Compare Source
v2.6.0 introduces a number of new features, including:
Example generation and verification of a signed in-toto statement:
Example container signing and verification using the new bundle format and referring artifacts:
Example usage of a signing config provided by the public good instance's TUF repository:
v2.6.0 leverages sigstore-go's signing and verification APIs gated behind these new flags. In an upcoming major release, we will be
updating Cosign to default to producing and consuming bundles to align with all other Sigstore SDKs.
Features
attest-blobthe ability to supply a complete in-toto statement, and add toverify-blob-attestationthe ability to verify with just a digest (#4306)Breaking API Changes
sign.SignerFromKeyOptsno longer generates a key. Instead, it returns whether or not the client needs to generate a key, and if so, clientsshould call
sign.KeylessSigner. This allows clients to more easily manage key generation.Bug Fixes
v2.5.3Compare Source
Features
Bug Fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.