-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add blog post for Cosign 2.0 released #24
Conversation
Signed-off-by: Hayden Blauzvern <[email protected]>
/HOLD This should not be released until the 23rd or when we release Cosign 2.0. |
Signed-off-by: Hayden Blauzvern <[email protected]>
Signed-off-by: Hayden Blauzvern <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm, thanks for doing that!
cc @bobcallaway @priyawadhwa for review |
Signed-off-by: Hayden Blauzvern <[email protected]>
Signed-off-by: Hayden Blauzvern <[email protected]>
Do you want to mention that anyone using --force/-f in cosign 1 needs to use --yes in cosign 2? I recognize that --yes was there in cosign 1 also, but in practice all the GitHub Actions I've seen were using --force which is gone. Any GitHub Action that looks like this is going to break with the transition:
|
Summary
Release Note
Documentation