-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Sign the artifacts (binaries/images) using cosign #2462
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
Labels
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
Do the maintainers think this is a good idea? i can implement the tiny bits if y'all agree |
I do think it's a good idea, and I'm willing to chime in with the implementation as well. |
scop
added a commit
to scop/golangci-lint
that referenced
this issue
May 10, 2025
scop
added a commit
to scop/golangci-lint
that referenced
this issue
May 11, 2025
scop
added a commit
to scop/golangci-lint
that referenced
this issue
May 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Your feature request related to a problem? Please describe.
Not a problem, is a feature request.
The idea is to sign the release artifacts using cosign when doing the release.
The project is already using GoReleaser and GitHub actions and that makes things easier to implement 😃
This is an initial step for a more secure release and lets the consumers have the ability to verify the release artifacts.
I can help to implement this feature if the team decides to move this idea forward.
Describe the solution you'd like.
Using the current GoRelease config and the GitHub Actions we can sign the binaries/images using a keyless approach and push the signed artifacts all together to the GitHub release.
Describe alternatives you've considered.
n/a
Additional context.
n/a
The text was updated successfully, but these errors were encountered: