CARGO-UPDATE(1)

💖 NAME 💖

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

okay so this is a page from the General Commands Manual, and bestie, it's giving "my lockfile said what it said." ✨

---

🌸 SYNOPSIS 🌸

cargo update [options] spec

---

✨ DESCRIPTION ✨

This command updates the dependencies in your Cargo.lock file to the latest version. And if you don't even have a Cargo.lock file yet? No worries — it'll get created for you with the latest available versions. Main character behavior honestly. 💅

---

🎀 OPTIONS 🎀

💫 Update Options

• spec… — Update only the packages you actually name here. This flag can be specified multiple times (go off, list them all). Peep cargo-pkgid(1) for the SPEC format.

If you do specify packages with spec, then a conservative update of the lockfile happens. Translation: only the dependency named by SPEC gets updated. Its transitive dependencies get updated only if SPEC literally cannot be updated without updating them. Every other dependency stays locked at the version it's currently recorded at. No cap. 🔒

And if spec is not specified at all? Every single dependency gets updated. All of them. Periodt.

• --recursive — When you use this with spec, the dependencies of spec are forced to update as well. Cannot be used with --precise. It's giving "pick a lane." 🙈
• --precise precise — When used with spec, this lets you name a specific version number to set the package to. And if the package comes from a git repository, this can be a git revision — like a SHA hash or a tag. 🔥

Now, not recommended, but you can specify a yanked version of a package (nightly only). When possible, try other non-yanked SemVer-compatible versions, or go seek help from the maintainers of the package. Like, actually ask them. 🫶

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).

• -w, --workspace — Attempts to update only the packages defined in the workspace. Other packages get updated only if they don't already exist in the lockfile. This one's lowkey perfect for updating Cargo.lock after you've changed version numbers in Cargo.toml. 👑
• --dry-run — Displays what would be updated, but doesn't actually write the lockfile. Window shopping, but for dependencies. 🛍️

💫 Display Options

• -v, --verbose — Use verbose output. May be specified twice for "very verbose" output, which includes extra output like 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.
• -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.
• --color when — Control when colored output is used. Valid values are:
  • 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.
• --ignore-rust-version — Ignore rust-version specification in packages.
• --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 these 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.

• --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 bestie, 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.

• --frozen — Equivalent to specifying both --locked and --offline. Two-for-one, iconic. 🌈

💫 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 at https://rust-lang.github.io/rustup/overrides.html for more information about how toolchain overrides work.
• --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 at 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.

This option is only available on the nightly channel at https://doc.rust-lang.org/book/appendix-07-nightly-rust.html and requires the -Z unstable-options flag to enable (see #10098 at https://github.com/rust-lang/cargo/issues/10098).

• -h, --help — Prints help information.
• -Z flag — Unstable (nightly-only) flags to Cargo. Run cargo -Z help for details.

---

🦋 ENVIRONMENT 🦋

See the reference at https://doc.rust-lang.org/cargo/reference/environment-variables.html for details on environment variables that Cargo reads. 🌸

---

⭐ EXIT STATUS ⭐

• 0: Cargo succeeded. 🎉
• 101: Cargo failed to complete. 💀

---

🔥 EXAMPLES 🔥

1. Update all dependencies in the lockfile:

cargo update

2. Update only specific dependencies:

cargo update foo bar

3. 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 just read CARGO-UPDATE(1), straight from the General Commands Manual — go forth and update responsibly, your lockfile is gonna eat. 💅✨