Update module github.com/sigstore/cosign/v3 to v3.1.2 - #465
Open
renovate-rancher[bot] wants to merge 1 commit into
Open
Update module github.com/sigstore/cosign/v3 to v3.1.2#465renovate-rancher[bot] wants to merge 1 commit into
renovate-rancher[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate-rancher
Bot
force-pushed
the
renovate/github.com-sigstore-cosign-v3-3.x
branch
from
June 17, 2026 06:23
50a9be4 to
64d6b21
Compare
renovate-rancher
Bot
force-pushed
the
renovate/github.com-sigstore-cosign-v3-3.x
branch
3 times, most recently
from
July 9, 2026 06:04
e4815d7 to
ebd5dcf
Compare
renovate-rancher
Bot
force-pushed
the
renovate/github.com-sigstore-cosign-v3-3.x
branch
from
July 15, 2026 05:34
ebd5dcf to
af6a7b6
Compare
renovate-rancher
Bot
force-pushed
the
renovate/github.com-sigstore-cosign-v3-3.x
branch
from
July 25, 2026 05:31
af6a7b6 to
c776949
Compare
Contributor
Author
|
renovate-rancher
Bot
force-pushed
the
renovate/github.com-sigstore-cosign-v3-3.x
branch
from
July 28, 2026 05:33
c776949 to
c26dd78
Compare
renovate-rancher
Bot
force-pushed
the
renovate/github.com-sigstore-cosign-v3-3.x
branch
from
July 29, 2026 05:36
c26dd78 to
6258350
Compare
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
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:
v3.0.6→v3.1.2Release Notes
sigstore/cosign (github.com/sigstore/cosign/v3)
v3.1.2Compare Source
This may be the last Cosign v3.1 release, as we finish deprecations and removing unused functionality. Soon we'll start work on Cosign v4 where we will remove things that are currently deprecated. We'll continue to support Cosign v3, with it's opt-in backwards compatibility, as described in our versioning policy.
If you haven't already, now is an excellent time to move to the bundle format that has been supported since Cosign v2.6.
We have received a ton of fixes over the past month from folks using Cosign in a variety of environments - thank you all!
Deprecations
816f2b6Deprecate --payload for sign and verify commands (#4991)Features
5121398docs: add OVHcloud KMS in available external plugins (#4962)38f73bbAdd insecure registry flag to ko publish in kind-verify-attestation workflow (#4970)2e0749aDeprecate --output-attestation (#4958)2233166Add bundle inspect command (#4842)Fixes
eb3bb86Guard against empty certificate PEM in mutate.Signature (#4998)089731cfix(download): Validate predicate type for new bundle formatd996ce1Skip nil subject entries in IntotoSubjectClaimVerifier (#5016)8ca5b20Fix Makefile: fall back to "unknown" version info when built outside a git repo (#5000)df78bf6fix(verify): skip identity validation for security keys (#5012)aebdc3afix: include artifactType in OCI 1.1 signature referrer manifestc0edaacAllow attestation download to handle both bundle types (#4996)a8642c7Fix panic in dockerfile verify on malformed FROM lines (#4979)ef3e3b4fix(release): restore signing-step auth and fail on image signing errors (#4978)16ddbcffeat(signing-config): add --base-config flag to override services from base config (#4977)f17f812fix: pass NewBundleFormat to KeyOpts in sign command (#4981)6ef8d9dfix: ignore build stage references in dockerfile verify (#4961)8dbdef5fix: allow '=' in annotation values (#4957)Cleanup
193d215Remove unused policy evaluation code (#4936)0fc9811Remove unused signing code (#4918)95dcedaRemove unused OCI code (#4935)b1dd2e9Remove unused ephemeral signer (#4938)Documentation
8184126feat: improve verify flag shell completions (#4965)ed0efe8docs: fix Short style and add Example fields to piv-tool subcommands (#4942)d41b86cdocs: add Example fields to env and bundle create commands (#4941)8a7174adocs: fix Short style and add Example fields to pkcs11-tool subcommandsThanks to all contributors!
v3.1.1Compare Source
What's Changed
Note: v3.1.0 was skipped due to a bug in our release pipeline. v3.1.1 is identical to v3.1.0
This release deprecates a number of flags related to verification material input for trust root material, as well as the bundle format, standardized across Sigstore SDKs, which is now the default output and input for signing and verifying respectively. You may continue to use the deprecated flags with Cosign v3.x releases. The deprecated flags will be removed in a future Cosign v4 release.
This release also updates the signing path for logging to Rekor v2. DSSE attestations will be logged as hashed entries, using the DSSE's pre-auth encoding (PAE). This should unblock developers who want to upload large signed DSSEs such as SBOMs.
Full Changelog: sigstore/cosign@v3.0.6...v3.1.1
v3.1.0Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.