Repository navigation
Retroactive CycloneDX SBOM for 1.5.0 (not for merging) - #6
Closed
jadamcrain wants to merge 1 commit into
Closed
jadamcrain wants to merge 1 commit into
jadamcrain wants to merge 1 commit into
Conversation
Member
Author
|
Done: the SBOM this produced is attached to the release (see the release assets). Closing without merging, as intended; this PR and its run remain the record of how the SBOM was generated. |
This was referenced Oct 9, 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
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.
Not for merging: this branch only runs a one-off workflow that produces a CycloneDX SBOM for the already-published 1.5.0 release, which will then be attached to that release. The published
.nupkgis not changed.How
The 1.5.0 release run's build logs are no longer available, so the workflow reproduces the release builds: rodbus
1.5.0with the release's exact arguments (-p rodbus-ffi --target <t> --no-default-features --features tls,crossfor Linux, the same MUSL flags), recording each build's log andcargo treeoutputs, then runs bom-tools 0.3.0. The crate set is fixed by the tag'sCargo.lock, the features and the targets, so it matches the shipped binaries. The allow list is rodbus's migratedallowed.json(stepfunc/rodbus#201, pinned commit).The result is checked against the
third-party-licenses.txtpublished with 1.5.0, which was produced from the original release build logs.