Move SBOM generation after release creation in release workflow #10501
Conversation
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
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
- Moved SBOM generation steps (SPDX and CycloneDX) to after release creation - Release is now created with binaries only, SBOM files uploaded separately - Added new step to upload SBOM files to existing release after generation - Updated specs/artifacts.md to reflect SBOM artifacts now uploaded from release job Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Move SBOM generation step after release creation
Move SBOM generation after release creation in release workflow
Jan 17, 2026
pelikhan
approved these changes
Jan 17, 2026
This was referenced Jan 17, 2026
Closed
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.
The release workflow was generating SBOM files before creating the GitHub release, then uploading both binaries and SBOMs atomically. This meant SBOM generation blocked the release creation.
Changes
gh release uploadto attach SBOMs to existing releaseWorkflow order
Before:
After:
This decouples SBOM generation from release creation, allowing the release to publish faster while still providing the same artifacts.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.