Correct stale SBOM comment in build workflow - #449
Merged
Conversation
btschwertfeger
added
Documentation
btschwertfeger
enabled auto-merge (squash)
July 30, 2026 06:37
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
1 participant
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.
PR #447 dropped the
gh release uploadstep that attachedsbom.cdx.jsonto the GitHub Release, since immutable releases make a release-time asset upload unworkable from a job triggered onrelease: created. The comment above the SBOM generation step still described that removed behavior.The SBOM now reaches consumers only as the digest-bound attestation written by
actions/attest-sbom, so the comment says that instead.