Add --locked to Rust cargo actions #2790
Open
Conversation
This file contains 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
This causes dependencies to be resolved in exactly the same way as they were in the Cargo.lock file, leading to more deterministic builds. Committing Cargo.lock and using this flag in CI is considered best practice, as suggested by the cargo book. https://doc.rust-lang.org/cargo/commands/cargo-build.html#manifest-options
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This causes dependencies to be resolved in exactly the same way as they were in the Cargo.lock file, leading to more deterministic builds. Committing Cargo.lock and using this flag in CI is considered best practice, as suggested by the cargo book.
https://doc.rust-lang.org/cargo/commands/cargo-build.html#manifest-options