Add SBOM generation to workflows and releases #187
Merged
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.
🗣 Description
This PR adds SBOM generation for each supported platform.
The SBOMs will be attached in an artifact for the workflow that generated the images.
If the workflow is part of a release or tag, the the SBOMs will be attached individually as assets to the release.
It also, cleans up some of the
name
tags in the build workflow.💭 Motivation and context
A “software bill of materials” (SBOM) has emerged as a key building block in software security and software supply chain risk management. A SBOM is a nested inventory, a list of ingredients that make up software components.
See:
🧪 Testing
Tested in ci-testing repository and in the v11 branch.
✅ Pre-approval checklist
to reflect the changes in this PR.