CARGO-UPDATE(1)

📦 version 1.82.0, in ubuntu jammy, ubuntu noble

✨ cargo-update(1) ✨

okay bestie, welcome to the cargo-update page from the General Commands Manual (section 1, she's official 💅). this is the one that goes and refreshes your deps for you. let's get into it 🫶

💖 NAME 💖

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

🌸 SYNOPSIS 🌸

cargo update [options] spec

🦋 DESCRIPTION 🦋

So here's the vibe: this command updates your dependencies in the Cargo.lock file to the latest version. slay.

And if the Cargo.lock file doesn't even exist yet? no worries bestie, it'll get created for you with the latest available versions. it's giving ✨manifestation✨.

🎀 OPTIONS 🎀

Update Options

  • spec… — Update only the specified packages. This flag may be specified multiple times (yes queen, stack 'em 👑). See cargo-pkgid(1) for the SPEC format.

Okay so here's the tea 🍵: if packages are specified with spec, then a conservative update of the lockfile will be performed. Translation? Only the dependency specified by SPEC will be updated. Its transitive dependencies will be updated only if SPEC cannot be updated without updating dependencies. Every other dependency stays locked at its currently recorded version. no cap.

And if spec is not specified? all dependencies are updated. go big or go home 💅.

  • --recursive — When used with spec, dependencies of spec are forced to update as well. Cannot be used with --precise. (they're exes, don't put them in the same room 💀)
  • --precise precise — When used with spec, this lets you specify a specific version number to set the package to. And if the package comes from a git repository, this can be a git revision (such as a SHA hash or tag). iconic 🧚

Now, while it's not recommended, you can specify a yanked version of a package. When possible, try other non-yanked SemVer-compatible versions or seek help from the maintainers of the package. (like, please, bestie, ask for help first 🙈)

A compatible pre-release version can also be specified even when the version requirement in Cargo.toml doesn't contain any pre-release identifier (nightly only).

  • --breaking directory — Update spec to latest SemVer-breaking version.

Version requirements will be modified to allow this update.

This only applies to dependencies when:

  • The package is a dependency of a workspace member
  • The dependency is not renamed
  • A SemVer-incompatible version is available
  • The "SemVer operator" is used (^ which is the default)
⚠️ This option is unstable and available only on the nightly channel <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html> and requires the -Z unstable-options flag to enable. See <https://github.com/rust-lang/cargo/issues/12425> for more information.
  • -w, --workspace — 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. (iykyk, this one's a lifesaver 🫶)
  • --dry-run — Displays what would be updated, but doesn't actually write the lockfile. it's the window shopping of cargo 🛍️

Display Options

  • -v, --verbose — Use verbose output. May be specified twice for "very verbose" output which includes extra output such as dependency warnings and build script output. May also be specified with the term.verbose config value <https://doc.rust-lang.org/cargo/reference/config.html>. (double it and give it to the next person 😭)
  • -q, --quiet — Do not print cargo log messages. May also be specified with the term.quiet config value <https://doc.rust-lang.org/cargo/reference/config.html>. shhh 🤫
  • --color when — 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 value <https://doc.rust-lang.org/cargo/reference/config.html>.

Manifest Options

  • --manifest-path path — Path to the Cargo.toml file. By default, Cargo searches for the Cargo.toml file in the current directory or any parent directory. (she'll find it, she always does 🔍)
  • --ignore-rust-version — Ignore rust-version specification in packages. (pretend you didn't see it 💀)
  • --locked — Asserts that the exact same dependencies and versions are used as when the existing Cargo.lock file was originally generated. Cargo will exit with an error when either of the following scenarios arises:
    • The lock file is missing.
    • Cargo attempted to change the lock file due to a different dependency resolution.

It may be used in environments where deterministic builds are desired, such as in CI pipelines. main character energy for CI ✨

  • --offline — 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 value <https://doc.rust-lang.org/cargo/reference/config.html>. airplane mode but make it cargo ✈️

  • **--frozen** — Equivalent to specifying both --lockedand--offline`. two for one, we love a bundle deal 🎁
  • --lockfile-path PATH — Changes the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing --lockfile-path will ignore existing lockfile at the default path, and instead will either use the lockfile from PATH, or write a new lockfile into the provided PATH if it doesn't exist. This flag can be used to run most commands in read-only directories, writing lockfile into the provided PATH.
⚠️ This option is only available on the nightly channel <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html> and requires the -Z unstable-options flag to enable (see #14421 <https://github.com/rust-lang/cargo/issues/14421>).

Common Options

  • +toolchain — 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 or +nightly). See the rustup documentation <https://rust-lang.github.io/rustup/overrides.html> for more information about how toolchain overrides work. pick your fighter 💅
  • --config KEY=VALUE or PATH — Overrides a Cargo configuration value. The argument should be in TOML syntax of KEY=VALUE, or provided as a path to an extra configuration file. This flag may be specified multiple times. See the command-line overrides section <https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides> for more information.
  • -C PATH — Changes the current working directory before executing any specified operations. This affects things like where cargo looks by default for the project manifest (Cargo.toml), as well as the directories searched for discovering .cargo/config.toml, for example. This option must appear before the command name, for example cargo -C path/to/my-project build. (order matters bestie, don't fight it 🫠)
⚠️ This option is only available on the nightly channel <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html> and requires the -Z unstable-options flag to enable (see #10098 <https://github.com/rust-lang/cargo/issues/10098>).
  • -h, --help — Prints help information. (hi, hello, how are you 🫶)
  • -Z flag — Unstable (nightly-only) flags to Cargo. Run cargo -Z help for details. spicy mode 🌶️

🌈 ENVIRONMENT 🌈

See the reference <https://doc.rust-lang.org/cargo/reference/environment-variables.html> for details on environment variables that Cargo reads. (she reads. she's well-read. she's that girl 📚✨)

💀 EXIT STATUS 💀

  • 0: Cargo succeeded. ate, no crumbs 🎀
  • 101: Cargo failed to complete. it's giving tragedy 😭

⭐ EXAMPLES ⭐

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

👑 SEE ALSO 👑

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

and that's the whole page bestie, you're officially fluent in cargo-update 💖 this lil' queen lives in section 1 of the General Commands Manual, so when you need her again just pull up cargo-update(1) and she'll be right there. periodt. 💅🌸🦋

📦 where this page comes from