You've already forked dcmerge
chore(deps): update dependency sigstore/cosign to v3 #127
Reference in New Issue
Block a user
Delete Branch "renovate/sigstore-cosign-3.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v2.6.2->v3.0.4Release Notes
sigstore/cosign (sigstore/cosign)
v3.0.4Compare Source
v3.0.4 resolves https://github.com/sigstore/cosign/security/advisories/GHSA-whqx-f9j3-ch6m.
Changes
v3.0.3Compare Source
Thank you for all of your feedback on Cosign v3! v3.0.3 fixes a number of bugs reported by
the community along with adding compatibility for the new bundle format and attestation
storage in OCI to additional commands. We're continuing to work on compatibility with
the remaining commands and will have a new release shortly. If you run into any problems,
please file an issue
Changes
clean(#4539)saveandload(#4538)signcli package.cosign initialize(#4462)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
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 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 Renovate Bot.
795255cf1fto8c0e4effe38c0e4effe3toec2ca2ac69ec2ca2ac69to686aaaaac6686aaaaac6to4f70d42718chore(deps): update dependency sigstore/cosign to v3.0.4to chore(deps): update dependency sigstore/cosign to v3View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.