-
Notifications
You must be signed in to change notification settings - Fork 4
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
create sigstore signature for cli bundles #291
Conversation
Signed-off-by: MarkAckert <[email protected]>
Signed-off-by: MarkAckert <[email protected]>
Signed-off-by: MarkAckert <[email protected]>
Signed-off-by: MarkAckert <[email protected]>
Signed-off-by: MarkAckert <[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.
Changes makes sense!
LGTM! 😋
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.
Not very familiar with Sigstore bundles and how we plan to use them, but changes LGTM - thanks @MarkAckert 😋
They're replacing the GPG artifact signatures we've used up to now, and means we don't have to manage private keys anymore. We have instructions on how to use the sigstore bundles to validate artifacts on the zowe.org download page for PAX, SMPE and PSWI :-) . I'll add CLI in with the next release |
What It Does
This PR adds sigstore signatures to the SDK and CLI standalone packages.
How to Test
Run the workflow.
Review Checklist
I certify that I have: