-
-
Couldn't load subscription status.
- Fork 1.5k
feat: sign release artifacts with cosign #5793
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
base: main
Are you sure you want to change the base?
Conversation
| For key updates, see the [changelog](https://golangci-lint.run/product/changelog/#{{ .Major }}{{ .Minor }}{{ .Patch }}). | ||
| signs: |
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.
Non-CI goreleaser release runs should likely be done with --skip sign in order to not break after we add this.
| signs: | ||
| - signature: ${artifact}.cosign.bundle | ||
| cmd: cosign |
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 guess some docs how to verify downloads with cosign would not hurt. But we don't have any for verifying the sha256sums either, so not sure. #5806 contains changes for verifying in the installer script.
12b2fc0 to
6898794
Compare
6898794 to
840da20
Compare
840da20 to
7d7647b
Compare
|
Rebased and switched to the new bundle format. |
|
I don't forget this PR, but each time I look at it, I'm stuck with the same problems/questions.
|
Sample results in my fork (do not mind the changelog, scroll down to assets): https://github.com/scop/golangci-lint/releases/tag/v0.0.0
https://goreleaser.com/customization/binary_sign/?h=cosign#signing-with-cosign
Fixes #2462