Add missing --locked
to Cargo commands
#66
Merged
+20
−21
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.
The Cargo
--locked
argument ensures that Cargo will fail with an error ifCargo.lock
is out of sync withCargo.toml
, rather than the lockfile being silently updated.As such, in CI we should always be using
--locked
for projects that have committed their lockfile to Git (which should be the case for most projects other than those that are libraries).After seeing that
cnb-otel-collector
didn't use--locked
in all cases, I audited all of our Rust repos and found others missing--locked
too.GUS-W-18062544.