Pin crate dependency resolution - #283
Open
Silic0nS0ldier wants to merge 1 commit into
Open
Conversation
Silic0nS0ldier
force-pushed
the
pin-crates
branch
from
July 23, 2026 07:46
6b987d8 to
b1cec08
Compare
Author
|
CI errors look to be an unrelated issue ( |
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.
As of
@rules_rust0.71.1 non-root modules must pin their dependencies.This change landed in bazelbuild/rules_rust#4109.
https://github.com/bazelbuild/rules_rust/pull/4109/changes#diff-7a86616f74944ee7c3932ee97054ae586b1f28573393c592e3a3e9a7550e3eceR619-R634
Beyond being required, locking these dependencies also makes supply chain attacks more difficult. Elimination of the on-demand dependency resolution should also speed up builds a little.