fix(release): correct binary SBOM input and prepare 0.1.1 - #54
Merged
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
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.
The v0.1.0 workflow compiled the binary and passed all checks, but failed before publication because the SBOM action treats
pathas a directory. It received a.tar.gzarchive and invoked Syft withdir:.Scan the existing staged release directory and keep asset uploads in the final publication job. Advance workspace, Dashboard and image defaults to 0.1.1, update verification examples, and preserve the failed v0.1.0 tag. Include Cargo.lock in the binary archive and require Cargo package URLs in its SBOM: the stripped binary alone produced only a directory component. The documented inventory covers locked workspace dependencies, including optional/test crates. Application behavior is unchanged.
Validation: locked offline Cargo metadata, release/source Compose rendering and document links passed. Syft v1.42.3 reproduced the old directory-input failure and generated valid SPDX-2.3 with 366 inventory entries after the fix. The actual workflow verifier accepts the real inventory and rejects an empty SBOM. Final-head repository checks, PostgreSQL E2E, both CodeQL jobs and dependency review all passed. This follows the complete production-image validation in #52.