SBOM composite action workflow #226
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
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.
Description
Add automatic SBOM generation to releases generated by github actions.
This will eventually be added to many repos, so the SBOM conversion is separated into a separate action which can be reused by other repos.
Motivation and Context
Improved transparency on dependency versions and licenses.
How Has This Been Tested?
This is a bit tricky. The majority of the action has been tested by creating releases on forks https://github.com/jeffreyparker/duo_client_python/actions/runs/5391813505 , but a full end-to-end test isn't possible until a real release is created.
Types of Changes