feat:added signed releases #1739
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
daemon1024
requested changes
Apr 23, 2024
krisharyan117
force-pushed
the
signed-releases
branch
from
2347563 to
a9c8975
Compare
daemon1024
approved these changes
Apr 23, 2024
rootxrishabh
approved these changes
Apr 23, 2024
|
We are getting CI fixed, will merge after that |
kranurag7
reviewed
Apr 23, 2024
daemon1024
force-pushed
the
signed-releases
branch
from
a9c8975 to
0d4c839
Compare
Signed-off-by: KrishAryan <[email protected]> replaced install karmor with install co-sign Signed-off-by: KrishAryan <[email protected]>
daemon1024
force-pushed
the
signed-releases
branch
from
0d4c839 to
5cb064e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of PR?:
The purpose of PR is to add signed releases feature to kubearmor artifacts using co-sign to increase OpenSSF scorecard score
Fixes #1532
Does this PR introduce a breaking change?
No
If the changes in this PR are manually verified, list down the scenarios covered::
No we just did some changes in goreleaser and ci-systemd-release workflow and tested things using OpenSSF scorecard
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
We still need to provide SLSA provenance file to increase OpenSSF score for signed releases for 8 to 10
Checklist:
<type>(<scope>): <subject>