Hotfix: Add the missing SBOM stage for release status#137
Merged
Conversation
canack
previously approved these changes
Nov 26, 2025
|
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
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.



Add SBOM Support to Release Status Command
Changes
- Added SBOM field to ReleaseStatus struct
- Added --sbom flag for filtering SBOM-specific status checks
- Updated status table output to include SBOM column
- Added SBOM failure detection in isReleaseFailed function
- Fixed verbose mode to skip scan detail fetch for SBOM (SBOM has no scan_id field)
Testing
Expected Behavior After Fix
s1: the release status is failed due to SBOM rules

s2: the SBOM related rules are passed successfully
