-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed #67
Closed
Conversation
This file contains 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
renovate
bot
force-pushed
the
renovate/github.com-sigstore-cosign-2.x
branch
2 times, most recently
from
September 12, 2023 08:20
796aebf
to
93c6a83
Compare
Pull Request Test Coverage Report for Build 6156791357
💛 - Coveralls |
renovate
bot
force-pushed
the
renovate/github.com-sigstore-cosign-2.x
branch
from
October 31, 2023 14:35
93c6a83
to
b77c111
Compare
renovate
bot
force-pushed
the
renovate/github.com-sigstore-cosign-2.x
branch
from
November 1, 2023 08:42
b77c111
to
1831716
Compare
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
Nov 8, 2023
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
chore(deps): update module github.com/sigstore/cosign to v2
Nov 10, 2023
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
Nov 10, 2023
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
chore(deps): update module github.com/sigstore/cosign to v2
Nov 10, 2023
renovate
bot
force-pushed
the
renovate/github.com-sigstore-cosign-2.x
branch
from
November 10, 2023 15:41
1831716
to
6519c15
Compare
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
Nov 11, 2023
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
chore(deps): update module github.com/sigstore/cosign to v2
Nov 11, 2023
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
Dec 8, 2023
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
chore(deps): update module github.com/sigstore/cosign to v2
Dec 8, 2023
renovate
bot
force-pushed
the
renovate/github.com-sigstore-cosign-2.x
branch
from
December 8, 2023 22:18
91dfd39
to
e600722
Compare
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
Dec 9, 2023
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
chore(deps): update module github.com/sigstore/cosign to v2
Dec 9, 2023
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
Dec 9, 2023
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
chore(deps): update module github.com/sigstore/cosign to v2
Dec 9, 2023
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
Dec 10, 2023
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
chore(deps): update module github.com/sigstore/cosign to v2
Dec 10, 2023
renovate
bot
changed the title
chore(deps): update module github.com/sigstore/cosign to v2
chore(deps): update module github.com/sigstore/cosign to v2 - autoclosed
Dec 11, 2023
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:
v1.13.1
->v2.2.2
Release Notes
sigstore/cosign (github.com/sigstore/cosign)
v2.2.2
Compare Source
v2.2.2 adds a new container with a shell,
gcr.io/projectsigstore/cosign:vx.y.z-dev
, in addition to the existingcontainer
gcr.io/projectsigstore/cosign:vx.y.z
without a shell.For private deployments, we have also added an alias for
--insecure-skip-log
,--private-infrastructure
.Bug Fixes
Features
--yes
flagcosign import-key-pair
to skip the overwrite confirmation. (#3383)Container Updates
Documentation
Contributors
v2.2.1
Compare Source
Note: This release comes with a fix for CVE-2023-46737 described in this Github Security Advisory. Please upgrade to this release ASAP
Enhancements
--only
flag incosign copy
to copy sign, att & sbom (#3247)Bug Fixes
SignedEntity
to be more descriptive (#3233)Documentation
Others
Contributors
v2.2.0
Compare Source
Enhancements
Bug Fixes
Documentation
Others
Contributors
v2.1.1
Compare Source
Bug Fixes
Documentation
Contributors
v2.1.0
Compare Source
Breaking Change: The predicate is now a required flag in the attest commands, set via the --type flag.
Enhancements
sign --sign-container-identity
CLI (#2984)attachment-tag-prefix
forcosign copy
(#3014)Digest
to theSignedEntity
interface. (#2960)Bug Fixes
Documentation
Contributors
Thank you to our contributors!
v2.0.2
Compare Source
Enhancements
Bug Fixes
SOURCE_DATE_EPOCH
for OCI CreatedAt times (#2878)Documentation
kms_support
docs (#2900)Contributors
v2.0.1
Compare Source
Enhancements
Bug Fixes
Contributors
v2.0.0
Compare Source
This is the official 2.0.0 release of cosign!
There are many new features and breaking changes from version 1.x, for a full explanation please read the Cosign 2.0 blog post.
Breaking Changes
COSIGN_EXPERIMENTAL=1
is no longer required to have identity-based ("keyless") signing and transparency.--tlog-upload=false
.--insecure-ignore-tlog=true
when verifying an artifact that was not uploaded to Rekor.--certificate-identity
and--certificate-oidc-issuer
. Like verifying a signature with a public key, it's critical to specify who you trust to generate a signature for identity-based signing. See #2056 for more discussion on this change.cosign verify --key <key.pem>
. We are actively working on more support for custom certificates for those who want to bring their existing PKI.cosign sign container.registry.io/foo:tag
. This is considered insecure since tags are mutable. If you want to specify a particular image, you are recommended to do so by digest.--insecure-ignore-sct=true
to skip this check.SIGSTORE_TRUST_REKOR_API_PUBLIC_KEY
has been removed. For private deployments, if you would like to set the Rekor public key to verify transparency log entries, use either a TUF setup or setSIGSTORE_REKOR_PUBLIC_KEY
with the PEM of the custom Rekor public key..--certificate
or--bundle
.cosign attest --type {custom|vuln}
(andcosign verify-attestation
) will now use the RFC 3986 compliant URIs, adding https://, so that these predicate types are compliant with the in-toto specification.--force
has been removed. To skip any prompts, use--yes
.Improvements
--certificate-identity=email
, you can set an environment variable forCOSIGN_CERTIFICATE_IDENTITY=email
.--offline=true
removes the fallback to the Rekor log when verifying an artifact. Previously, if you did not provide a bundle (a persisted response from Rekor), Cosign would fallback to querying Rekor. You can now skip this fallback for offline environments. Note that if the bundle fails to verify, Cosign will not fallback and will fail early.--issue-certificate=true
with a key,--key
, or security key,--sk
. This is useful when adopting Sigstore incrementally.cosign sign --timestamp-server-url=<url> <container>
, such as https://freetsa.org/tsr, and to verify,cosign verify --timestamp-certificate-chain=<path-to-PEM-encodeded-chain> <other flags> <artifact>
.cosign sign-blob --timestamp-server-url=<url> --rfc3161-timestamp=<output-path> --bundle=<output-path> <blob>
, and to verify,cosign verify-blob --rfc3161-timestamp=<output-path> --timestamp-certificate-chain=<path-to-PEM-encoded-chain> --bundle=<output-path> <other flags> <blob>
.For specific PRs representing enhancements, bug fixes, documentation, and breaking changes, please see the sections below for prereleases v2.0.0-rc.0, v2.0.0-rc.1, v2.0.0-rc.2, and v2.0.0-rc.3.
Thanks to all contributors!
v1.13.2
Compare Source
What's Changed
Full Changelog: sigstore/cosign@v1.13.1...v1.13.2
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 has been generated by Mend Renovate. View repository job log here.