table of contents
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 if there are any manifest changes or dependency updates.
See also cargo-update(1) which is also capable of creating a Cargo.lock lockfile and has more options for controlling update behavior.
May also be specified with the term.color config value <https://doc.rust-lang.org/cargo/reference/config.html>.
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.
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 value <https://doc.rust-lang.org/cargo/reference/config.html>.
See the reference <https://doc.rust-lang.org/cargo/reference/environment-variables.html> for details on environment variables that Cargo reads.