cargo-update - Update dependencies as recorded in the local lock file
This command will update dependencies in the Cargo.lock file to the
latest version. If the Cargo.lock file does not exist, it will be
created with the latest available versions.
-p spec..., --package spec...
Update only the specified packages. This flag may be
specified multiple times. See cargo-pkgid(1)
for the SPEC format.
If packages are specified with the -p flag, then a
conservative update of the lockfile will be performed. This means that only
the dependency specified by SPEC will be updated. Its transitive
dependencies will be updated only if SPEC cannot be updated without updating
dependencies. All other dependencies will remain locked at their currently
If -p is not specified, all dependencies are updated.
When used with -p, dependencies of spec are
forced to update as well. Cannot be used with --precise.
When used with -p, allows you to specify a
specific version number to set the package to. If the package comes from a git
repository, this can be a git revision (such as a SHA hash or tag).
Attempt to update only packages defined in the workspace.
Other packages are updated only if they don't already exist in the lockfile.
This option is useful for updating Cargo.lock after you've changed
version numbers in Cargo.toml.
Displays what would be updated, but doesn't actually
write the lockfile.
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.Update all dependencies in the lockfile:
2.Update only specific dependencies:
cargo update -p foo -p bar
3.Set a specific dependency to a specific version:
cargo update -p foo --precise 1.2.3