release: default to vendored deps for katana binary builds#442
Open
release: default to vendored deps for katana binary builds#442
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #442 +/- ##
==========================================
- Coverage 73.32% 68.08% -5.25%
==========================================
Files 209 277 +68
Lines 23132 33386 +10254
==========================================
+ Hits 16961 22730 +5769
- Misses 6171 10656 +4485 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Objective
Make vendored dependencies the default input for Katana binary release builds, and enforce them in CI/release workflows.
Why vendoring is required for hermetic reproducibility
A reproducible build requires all inputs to be fixed, local, and verifiable; relying on live crates.io/git fetches introduces mutable external state (e.g., crates on crates.io can get deleted, or modified while still keeping the same version tag).
This is the same reproducibility direction established in #441, applied to the Katana binary release pipeline.
Why the tarball is split into multiple parts
GitHub hard-rejects files above 100 MB, so a single vendor archive cannot be committed directly.
The archive is split into deterministic
vendor.tar.gz.part-*chunks (<100 MB each), then reconstructed and checksum-verified during CI/build.What this PR changes
release.ymlbuild from vendored inputs by default.Cargo.lockvs vendor artifacts) and a double-build hash reproducibility gate.Related