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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: SBOM references wrong tag for slash-containing branches
The SBOM generation step uses
github.ref_namedirectly as the Docker image tag, but the build step usessteps.meta.outputs.tagsfromdocker/metadata-action. The metadata action sanitizes branch names by converting slashes to hyphens (e.g.,feature/foobecomesfeature-foo), whilegithub.ref_namereturns the raw branch name with slashes. For branches containing slashes, the SBOM step will attempt to scan an image tag that doesn't exist, causing the workflow to fail.