Repository navigation
Generate the license report and a CycloneDX SBOM with bom-tools 0.3.0 - #8
Merged
Merged
Conversation
Same migration as stepfunc/rodbus#201: each build records its evidence with upstream's build-evidence.sh, packaging runs bom-tools 0.3.0 for the license report and the SBOM, the SBOM is embedded in the .nupkg and attached to the release. The upstream ref is now a single RODBUS_REF variable.
jadamcrain
marked this pull request as draft
October 9, 2026 22:57
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.
Closes #7.
Same migration as stepfunc/rodbus#201 upstream, so CI is in place before the next release.
Changes
RODBUS_REF: one variable for the upstream ref, instead of the sameref:in three checkouts. Between releases it points at upstreammain(now ec1a587, the first commit with the evidence script and the migratedallowed.json), so this repo's CI keeps checking that upstream builds without serial.cross): upstream's.github/scripts/build-evidence.shwith this repo's arguments (--no-default-features --features tls); it builds and recordsbuild.json,tree.txtandruntime-tree.txt. The evidence is uploaded asevidence-<target>.--tag 0.3.0(replaces allow-list 0.2.1) producesthird-party-licenses.txtandsboms/rodbus-ffi.cdx.json; the SBOM is uploaded, and embedded in the.nupkgnext to the license report.rodbus-ffi.cdx.jsonas well, and first checks thatRODBUS_REFequals the tag being released, so a release can't package an unreleased upstream commit.Releasing
Set
RODBUS_REFto the upstream release tag (same version as this repo's tag), then tag this repo.Same steps as the retroactive SBOM in #6. An all-targets approval check of upstream
main'sallowed.jsonfor thesetls-only builds finds no problems.