Don't publish the SBOM back to Github #1785
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.
Please select one of the following
Summary
Our CI would generate the SBOM, and then commit all files and push back to Github as part of a version update. That meant the SBOM manifest was also picked up. Let's move the "Generate and Publish SBOM" steps to after the "Push back to Github" steps so they aren't picked up. Let's also remove the manifest files.
Changelog
[INTERNAL] [CHANGED] - Don't publish the SBOM back to Github
Test Plan
I'll keep an eye on the next publish.