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.
To provide transparency in the supply chain of the release, cosign (a client for Sigstore) is used to sign the SBOM. It is now common to provide signed artifacts and later on, before deployment, verify the SBOM's signature. This ensures integrity and authenticity (the SBOM has not been tampered with and, only authorized entities - the GitHub runner - produces/signs the SBOM)
Changes
Added two steps in the
auto-release.yml
, right after generating the SBOM, before commiting the changes.It is easy to reproduce locally. Install
cosign
. Download the release. Run the two commands added in theattest sbom
step. The first command (cosign sign-blob) should produce two files. As a sanity check, the second command verifies the signature, plus that the entity that signed is indeed the GitHub runner.Checklist:
Related Issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.