Provided by: cargo_0.47.0-1~exp1ubuntu1~16.04.1_amd64 bug


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


       cargo update [OPTIONS]


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


   Update Options
       -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 recorded versions.

           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.

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

           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 which includes
           extra output such as dependency warnings and build script output. May also be
           specified with the term.verbose config value

       -q, --quiet
           No output printed to stdout.

       --color WHEN
           Control when colored output is used. Valid values:

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

           •   always: Always display colors.

           •   never: Never display colors.

           May also be specified with the term.color config value

   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.

       --frozen, --locked
           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

           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

   Common Options
           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 <> for more
           information about how toolchain overrides work.

       -h, --help
           Prints help information.

       -Z FLAG...
           Unstable (nightly-only) flags to Cargo. Run cargo -Z help for details.


       See the reference <>
       for details on environment variables that Cargo reads.


           Cargo succeeded.

           Cargo failed to complete.


        1. Update all dependencies in the lockfile:

               cargo update

        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


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

                                            2019-09-05                            CARGO-UPDATE(1)