Install Rust tools with --locked by default or add a parameter to allow this

[mlegner]

search you tried in the issue tracker

rust locked

describe your actual problem

Many (most?) Rust projects come with lock files that specify the exact versions of dependencies with which they are tested. Sometimes, they don't work with newer versions, which is why Cargo offers the --locked parameter to build with the dependency versions specified in the lock files.

Currently, pre-commit installs Rust tools without the --locked parameter. I suggest to use this parameter by default or offer a way to specify that a hook should be built using that parameter.

pre-commit --version

pre-commit 3.6.2

[asottile]

does cargo not use the lock file if present by default? I was under the impression that --locked is only necessary to produce an error if it is missing

[mlegner]

does cargo not use the lock file if present by default?

No, the lock file is ignored by default.

[asottile]

hmmmmm I think additional_dependencies: [--locked] will work

[mlegner]

No, unfortunately this doesn't seem to work as an @* is added automatically:

An unexpected error has occurred: CalledProcessError: command: ('~/.cargo/bin/cargo', 'add', '--locked@*')
return code: 1
stdout: (none)
stderr:
    error: unexpected argument '--locked@*' found
    
      tip: a similar argument exists: '--locked'
    
    Usage: cargo add [OPTIONS] <DEP>[@<VERSION>] ...
           cargo add [OPTIONS] --path <PATH> ...
           cargo add [OPTIONS] --git <URL> ...
    
    For more information, try '--help'.