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
Mentioned required cosign version for the --certificate
flag
#39080
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
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.
Thanks. This'll want tech review from someone who can confirm that's how cosign
works.
{{< note >}} | ||
cosign v1.9.0 is required to be able to use the `--certificate` flag. | ||
Please use `--cert` for older versions of cosign. | ||
{{< /note >}} |
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.
I suggest making the following paragraph not be a note. The page will read better as a result, and people will still see the link to learn more.
Extra credit: copy that link to a “what's next” section at the foot of the page (see other tasks pages for an example)
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.
I removed the note
. Regarding the "What's next" section: What should we expect content wise there? Wouldn't we duplicate information if mentioning again that cosign has to be up to date? We could link to the cosign changelog and show how it can be updated, though.
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.
In docs, it's OK to duplicate information from earlier into the page into the What's Next section.
Something like this:
## {{% heading "whatsnext" %}}
Read
[Keyless Signatures](https://github.com/sigstore/cosign/blob/main/KEYLESS.md#keyless-signatures)
to learn more about Sigstore keyless signing.
Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
1689d1e
to
09d013b
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tengqm The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@saschagrunert could you recommend a tech reviewer for this? I'm happy to LGTM it for SIG Docs. |
/lgtm |
LGTM label has been added. Git tree hash: 19d0c17eafa27dbd5a5bfdd13e3ad37a5c855d3f
|
Fixes #38473