Add support for hosting SPDX-2 SBOMs alongside release artifacts #2359
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.
Part 1 of #2339
I modeled this PR off of the Sigstore bundle PR since it's a very similar approach.
There may be more than one SBOM per artifact eventually (for multiple reasons, either users demanding CycloneDX or a new major version of SPDX) so accounting for that possibility by using
spdx2
as the prefix for the database field.I don't know what the "admin" interface needs to look like for release managers to be able to submit SBOM files for new releases, this might already be enough if Sigstore bundles are doable today.