build: Use cargo-auditable for rust build#334
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #334 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 56 56
Lines 3406 3406
=========================================
Hits 3406 3406 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
This PR updates the release build workflow to produce Rust-based wheel artifacts that embed dependency metadata using cargo-auditable, enabling downstream auditing/scanning of shipped binaries.
Changes:
- Install
cargo-auditableduring release builds (host install for macOS/Windows; container install for Linux). - Configure release builds to wrap Rust compilation with
cargo-auditableand disablesccachefor compatibility.
Oliver Borchert (borchero)
left a comment
There was a problem hiding this comment.
I haven't used cargo-auditable before but seems fine 😄
|
FTR, I manually checked for the relevant linker section in all binaries using |
Co-authored-by: Daniel Elsner <dvelsner@gmail.com>
Co-authored-by: Daniel Elsner <dvelsner@gmail.com>
| if [[ "$RUNNER_OS" != "Linux" ]]; then | ||
| cargo install cargo-auditable@0.7.4 --locked | ||
| fi |
There was a problem hiding this comment.
split into separate conditional steps.
Motivation
Make release rust binaries auditable, e.g., for vulnerability scanning of included crates.
Changes
Use
cargo-auditablefor release builds on PyPI.cargo-auditableworks by embedding data about the dependency tree in JSON format into a dedicated linker section of the compiled executable.