cargo-generate-lockfile - Generate the lockfile for a package
cargo generate-lockfile [options]
This command will create the Cargo.lock lockfile for the current package
or workspace. If the lockfile already exists, it will be rebuilt with the
latest available version of every package.
See also cargo-update(1) which is also capable of creating
a Cargo.lock lockfile and has more options for controlling update
No output printed to stdout.
Control when colored output is used. Valid values:
•auto (default): Automatically detect if
color support is available on the terminal.
•always: Always display colors.
•never: Never display colors.
May also be specified with the term.color config
Path to the Cargo.toml file. By default, Cargo
searches for the Cargo.toml file in the current directory or any parent
Either of these flags requires that the Cargo.lock
file is up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen
flag also prevents Cargo
from attempting to access the network to determine if it is out-of-date.
These may be used in environments where you want to assert that
the Cargo.lock file is up-to-date (such as a CI build) or want to
avoid network access.
Prevents Cargo from accessing the network for any reason.
Without this flag, Cargo will stop with an error if it needs to access the
network and the network is not available. With this flag, Cargo will attempt
to proceed without the network if possible.
Beware that this may result in different dependency resolution
than online mode. Cargo will restrict itself to crates that are downloaded
locally, even if there might be a newer version as indicated in the local
copy of the index. See the cargo-fetch(1) command to download
dependencies before going offline.
May also be specified with the net.offline config
If Cargo has been installed with rustup, and the first
argument to cargo
begins with +
, it will be interpreted as a
rustup toolchain name (such as +stable
). See the
for more information
about how toolchain overrides work.
Prints help information.
Unstable (nightly-only) flags to Cargo. Run cargo -Z
help for details.
•0: Cargo succeeded.
•101: Cargo failed to complete.
1.Create or update the lockfile for the current package