fix(ci): add --locked to cargo install#548
Merged
Merged
Conversation
emlautarom1
approved these changes
Jul 15, 2026
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
2 participants
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.
Changes
Add
--lockedto everycargo installinvocation across all CI workflows.Reason
cargo install <tool>@<ver>without--lockedre-resolves the tool's dependency tree to the newest semver-compatible versions at install time, ignoring theCargo.lockits maintainers shipped and tested. Forcargo-deny@0.19.0this pulls inkstring@2.0.3(MSRV 1.96.0), which fails to build on the toolchain pinned to1.95.0inrust-toolchain.toml— breaking thedependency-auditworkflow.--lockedforces cargo to use each tool's bundled lockfile — the versions vetted against that tool's own MSRV — so no MSRV-exceeding transitive upgrade sneaks in. Applying it to everycargo install(not just the one that broke) hardens the rest against the same latent hazard and is standard practice for reproducible CI.