cargo update

NAME

cargo-update - Update dependencies as recorded in the local lock file

SYNOPSIS

cargo update [OPTIONS]

DESCRIPTION

This command will update dependencies in the Cargo.lock file to the latestversion. It requires that the Cargo.lock file already exists as generatedby commands such as cargo-build(1) or cargo-generate-lockfile(1).

OPTIONS

Update Options

  • -pSPEC…​
  • —packageSPEC…​
  • Update only the specified packages. This flag may be specifiedmultiple times. See cargo-pkgid(1) for the SPEC format.

If packages are specified with the -p flag, then a conservative update ofthe lockfile will be performed. This means that only the dependency specifiedby SPEC will be updated. Its transitive dependencies will be updated only ifSPEC cannot be updated without updating dependencies. All other dependencieswill remain locked at their currently recorded versions.

If -p is not specified, all dependencies are updated.

  • —aggressive

  • When used with -p, dependencies of SPEC are forced to update as well.Cannot be used with —precise.

  • —precisePRECISE

  • When used with -p, allows you to specify a specific version number toset the package to. If the package comes from a git repository, this canbe a git revision (such as a SHA hash or tag).

  • —dry-run

  • Displays what would be updated, but doesn’t actually write the lockfile.

Display Options

  • -v
  • —verbose

  • Use verbose output. May be specified twice for "very verbose" output whichincludes extra output such as dependency warnings and build script output.May also be specified with the term.verboseconfig value.

  • -q

  • —quiet

  • No output printed to stdout.

  • —colorWHEN

  • Control when colored output is used. Valid values:

  • auto (default): Automatically detect if color support is available on theterminal.

  • always: Always display colors.

  • never: Never display colors.

May also be specified with the term.colorconfig value.

Manifest Options

  • —manifest-pathPATH

  • Path to the Cargo.toml file. By default, Cargo searches in the currentdirectory or any parent directory for the Cargo.toml file.

  • —frozen

  • —locked
  • Either of these flags requires that the Cargo.lock file isup-to-date. If the lock file is missing, or it needs to be updated, Cargo willexit with an error. The —frozen flag also prevents Cargo fromattempting to access the network to determine if it is out-of-date.

These may be used in environments where you want to assert that theCargo.lock file is up-to-date (such as a CI build) or want to avoid networkaccess.

  • —offline
  • Prevents Cargo from accessing the network for any reason. Without thisflag, Cargo will stop with an error if it needs to access the network andthe network is not available. With this flag, Cargo will attempt toproceed without the network if possible.

Beware that this may result in different dependency resolution than onlinemode. Cargo will restrict itself to crates that are downloaded locally, evenif 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 goingoffline.

May also be specified with the net.offline config value.

Common Options

  • -h
  • —help

  • Prints help information.

  • -ZFLAG…​

  • Unstable (nightly-only) flags to Cargo. Run cargo -Z help fordetails.

ENVIRONMENT

See the reference fordetails on environment variables that Cargo reads.

Exit Status

  • 0

  • Cargo succeeded.

  • 101

  • Cargo failed to complete.

EXAMPLES

  • Update all dependencies in the lockfile:
  1. cargo update
  • Update only specific dependencies:
  1. cargo update -p foo -p bar
  • Set a specific dependency to a specific version:
  1. cargo update -p foo --precise 1.2.3

SEE ALSO

cargo(1), cargo-generate-lockfile(1)