chore(deps): update dependency cosign to v3

[renovate]

This PR contains the following updates:

Package	Update	Change
cosign	major	2.5.2 -> 3.0.2

---

Release Notes

sigstore/cosign (cosign)

v3.0.2

Compare 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.

• Note that the --bundle flag specifying an output file to write the Sigstore bundle (which contains all relevant verification material) has moved from optional to required in v3.

Changes

• choose different signature filename for KMS-signed release signatures (#​4448)
• Update rekor-tiles version path (#​4450)

v3.0.1

Compare Source

v3.0.1 is an equivalent release to v3.0.0, which was never published due to a failure in our CI workflows.

• Note that the --bundle flag specifying an output file to write the Sigstore bundle (which contains all relevant verification material) has moved from optional to required in v3.

Changes

• update goreleaser config for v3.0.0 release (#​4446)

v2.6.1

Compare Source

Bug Fixes

• Partially populate the output of cosign verify when working with new bundles (#​4416)
• Bump sigstore-go, move conformance back to tagged release (#​4426)

v2.6.0

Compare Source

v2.6.0 introduces a number of new features, including:

• Signing an in-toto statement rather than Cosign constructing one from a predicate, along with verifying a statement's subject using a digest and digest algorithm rather than providing a file reference (#​4306)
• Uploading a signature and its verification material (a "bundle") as an OCI Image 1.1 referring artifact, completing #​3927 (#​4316)
• Providing service URLs for signing and attesting using a SigningConfig. Note that this is required when using a Rekor v2 instance (#​4319)

Example generation and verification of a signed in-toto statement:

cosign attest-blob --new-bundle-format=true --bundle="digest-key-test.sigstore.json" --key="cosign.key" --statement="../sigstore-go/examples/sigstore-go-signing/intoto.txt"
cosign verify-blob-attestation --bundle="digest-key-test.sigstore.json" --key=cosign.pub --type=unused --digest="b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9" --digestAlg="sha256"

Example container signing and verification using the new bundle format and referring artifacts:

cosign sign --new-bundle-format=true ghcr.io/user/alpine@sha256:a19367999603840546b8612572e338ec076c6d1f2fec61760a9e11410f546733
cosign verify --new-bundle-format=true ghcr.io/user/alpine@sha256:a19367999603840546b8612572e338ec076c6d1f2fec61760a9e11410f546733

Example usage of a signing config provided by the public good instance's TUF repository:

cosign sign-blob --use-signing-config --bundle sigstore.json README.md
cosign verify-blob --new-bundle-format --bundle sigstore.json --certificate-identity $EMAIL --certificate-oidc-issuer $ISSUER --use-signed-timestamps README.md

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

• Add to attest-blob the ability to supply a complete in-toto statement, and add to verify-blob-attestation the ability to verify with just a digest (#​4306)
• Have cosign sign support bundle format (#​4316)
• Add support for SigningConfig for sign-blob/attest-blob, support Rekor v2 (#​4319)
• Add support for SigningConfig in sign/attest (#​4371)
• Support self-managed keys when signing with sigstore-go (#​4368)
• Don't require timestamps when verifying with a key (#​4337)
• Don't load content from TUF if trusted root path is specified (#​4347)
• Add a terminal spinner while signing with sigstore-go (#​4402)
• Require exclusively a SigningConfig or service URLs when signing (#​4403)
• Remove SHA256 assumption in sign-blob/verify-blob (#​4050)
• Bump sigstore-go, support alternative hash algorithms with keys (#​4386)

Breaking API Changes

• sign.SignerFromKeyOpts no longer generates a key. Instead, it returns whether or not the client needs to generate a key, and if so, clients
  should call sign.KeylessSigner. This allows clients to more easily manage key generation.

Bug Fixes

• Verify subject with bundle only when checking claims (#​4320)
• Fixes to cosign sign / verify for the new bundle format (#​4346)

v2.5.3

Compare Source

Features

• Add signing-config create command (#​4280)
• Allow multiple services to be specified for trusted-root create (#​4285)
• feat: Add OCI 1.1+ experimental support to tree (#​4205)
• Add validity period end for trusted-root create (#​4271)

Bug Fixes

• Fix cert verification logic for trusted-root/SCTs (#​4294)
• force when copying the latest image to overwrite (#​4298)
• avoid double-loading trustedroot from file (#​4264)

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.