feat(gates): add sbom-compliance requirement as a release blocking#2731
Merged
Conversation
Signed-off-by: Victoria <kaysa.vps@gmail.com>
migmartri
previously approved these changes
Feb 12, 2026
Signed-off-by: Victoria <kaysa.vps@gmail.com>
kaysavps
force-pushed
the
gate-sbom-compliance
branch
from
18e5091 to
f6acf73
Compare
Contributor
Author
|
The GitHub UI showed conflicts that prevented the merge. It seems the problem was that the branch was too old and there were too many changes in main. |
jiparis
approved these changes
Feb 17, 2026
This file contains hidden or 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
3 participants
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.
This PR adds a control gate for the sbom-compliance requirement of the Chainloop Best Practices. All components in the SBOM should have a reported license and should not include any banned licenses (except for the declared exceptions).
refs #2732