diff --git a/src/bin/cargo/cli.rs b/src/bin/cargo/cli.rs index 95e5c0e8a..f4f04bb4f 100644 --- a/src/bin/cargo/cli.rs +++ b/src/bin/cargo/cli.rs @@ -640,7 +640,7 @@ See 'cargo help <>' for more information on a sp .value_parser(clap::builder::ValueParser::path_buf()), ) .arg( - flag("locked", "Require Cargo.lock to be up-to-date") + flag("locked", "Assert that `Cargo.lock` will remain unchanged") .help_heading(heading::MANIFEST_OPTIONS) .global(true), ) diff --git a/src/doc/man/generated_txt/cargo-add.txt b/src/doc/man/generated_txt/cargo-add.txt index b8981fd20..83e1dda7d 100644 --- a/src/doc/man/generated_txt/cargo-add.txt +++ b/src/doc/man/generated_txt/cargo-add.txt @@ -172,13 +172,18 @@ OPTIONS Add dependencies to only the specified package. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-bench.txt b/src/doc/man/generated_txt/cargo-bench.txt index f75e8ac82..7984879ac 100644 --- a/src/doc/man/generated_txt/cargo-bench.txt +++ b/src/doc/man/generated_txt/cargo-bench.txt @@ -339,13 +339,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-build.txt b/src/doc/man/generated_txt/cargo-build.txt index e6fc2616a..7d652e8eb 100644 --- a/src/doc/man/generated_txt/cargo-build.txt +++ b/src/doc/man/generated_txt/cargo-build.txt @@ -273,13 +273,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-check.txt b/src/doc/man/generated_txt/cargo-check.txt index 0cbb36a1a..bfc300360 100644 --- a/src/doc/man/generated_txt/cargo-check.txt +++ b/src/doc/man/generated_txt/cargo-check.txt @@ -258,13 +258,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-clean.txt b/src/doc/man/generated_txt/cargo-clean.txt index fb50ba7ec..066a70352 100644 --- a/src/doc/man/generated_txt/cargo-clean.txt +++ b/src/doc/man/generated_txt/cargo-clean.txt @@ -92,13 +92,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-doc.txt b/src/doc/man/generated_txt/cargo-doc.txt index f4b93a998..d6b0eb2af 100644 --- a/src/doc/man/generated_txt/cargo-doc.txt +++ b/src/doc/man/generated_txt/cargo-doc.txt @@ -229,13 +229,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-fetch.txt b/src/doc/man/generated_txt/cargo-fetch.txt index 37ecd928b..63fa205a3 100644 --- a/src/doc/man/generated_txt/cargo-fetch.txt +++ b/src/doc/man/generated_txt/cargo-fetch.txt @@ -72,13 +72,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-fix.txt b/src/doc/man/generated_txt/cargo-fix.txt index 81830bf1c..92b2d9d08 100644 --- a/src/doc/man/generated_txt/cargo-fix.txt +++ b/src/doc/man/generated_txt/cargo-fix.txt @@ -331,13 +331,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-generate-lockfile.txt b/src/doc/man/generated_txt/cargo-generate-lockfile.txt index 7e5dae062..d1951275e 100644 --- a/src/doc/man/generated_txt/cargo-generate-lockfile.txt +++ b/src/doc/man/generated_txt/cargo-generate-lockfile.txt @@ -47,13 +47,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-install.txt b/src/doc/man/generated_txt/cargo-install.txt index 2ba85c596..1e3621952 100644 --- a/src/doc/man/generated_txt/cargo-install.txt +++ b/src/doc/man/generated_txt/cargo-install.txt @@ -243,13 +243,18 @@ OPTIONS Manifest Options --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-metadata.txt b/src/doc/man/generated_txt/cargo-metadata.txt index dd670191a..f1f5b1fc2 100644 --- a/src/doc/man/generated_txt/cargo-metadata.txt +++ b/src/doc/man/generated_txt/cargo-metadata.txt @@ -405,13 +405,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-package.txt b/src/doc/man/generated_txt/cargo-package.txt index 1dbed5692..f24d09b75 100644 --- a/src/doc/man/generated_txt/cargo-package.txt +++ b/src/doc/man/generated_txt/cargo-package.txt @@ -159,13 +159,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-pkgid.txt b/src/doc/man/generated_txt/cargo-pkgid.txt index 00bcd4f3e..3123dcad2 100644 --- a/src/doc/man/generated_txt/cargo-pkgid.txt +++ b/src/doc/man/generated_txt/cargo-pkgid.txt @@ -85,13 +85,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-publish.txt b/src/doc/man/generated_txt/cargo-publish.txt index 16c401065..d0b32a158 100644 --- a/src/doc/man/generated_txt/cargo-publish.txt +++ b/src/doc/man/generated_txt/cargo-publish.txt @@ -129,13 +129,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-remove.txt b/src/doc/man/generated_txt/cargo-remove.txt index 5092dd94e..9d8c14afc 100644 --- a/src/doc/man/generated_txt/cargo-remove.txt +++ b/src/doc/man/generated_txt/cargo-remove.txt @@ -62,13 +62,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-run.txt b/src/doc/man/generated_txt/cargo-run.txt index e977975cb..0a86eaba1 100644 --- a/src/doc/man/generated_txt/cargo-run.txt +++ b/src/doc/man/generated_txt/cargo-run.txt @@ -177,13 +177,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-rustc.txt b/src/doc/man/generated_txt/cargo-rustc.txt index 878889cc1..e16633b7d 100644 --- a/src/doc/man/generated_txt/cargo-rustc.txt +++ b/src/doc/man/generated_txt/cargo-rustc.txt @@ -275,13 +275,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-rustdoc.txt b/src/doc/man/generated_txt/cargo-rustdoc.txt index 92c32864f..024796e2e 100644 --- a/src/doc/man/generated_txt/cargo-rustdoc.txt +++ b/src/doc/man/generated_txt/cargo-rustdoc.txt @@ -245,13 +245,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-test.txt b/src/doc/man/generated_txt/cargo-test.txt index a0b4c43fd..690fb31dd 100644 --- a/src/doc/man/generated_txt/cargo-test.txt +++ b/src/doc/man/generated_txt/cargo-test.txt @@ -365,13 +365,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-tree.txt b/src/doc/man/generated_txt/cargo-tree.txt index 0bd39986c..4037e7f0c 100644 --- a/src/doc/man/generated_txt/cargo-tree.txt +++ b/src/doc/man/generated_txt/cargo-tree.txt @@ -212,13 +212,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-update.txt b/src/doc/man/generated_txt/cargo-update.txt index a4b9c24f6..a1be485b9 100644 --- a/src/doc/man/generated_txt/cargo-update.txt +++ b/src/doc/man/generated_txt/cargo-update.txt @@ -82,13 +82,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-vendor.txt b/src/doc/man/generated_txt/cargo-vendor.txt index a46c2afe9..ab1e9a0f0 100644 --- a/src/doc/man/generated_txt/cargo-vendor.txt +++ b/src/doc/man/generated_txt/cargo-vendor.txt @@ -54,13 +54,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/generated_txt/cargo-verify-project.txt b/src/doc/man/generated_txt/cargo-verify-project.txt index 86736043b..aca632b5c 100644 --- a/src/doc/man/generated_txt/cargo-verify-project.txt +++ b/src/doc/man/generated_txt/cargo-verify-project.txt @@ -50,13 +50,18 @@ OPTIONS Cargo.toml file in the current directory or any parent directory. --locked - Requires the Cargo.lock file be up-to-date. If the lock file is - missing, or it needs to be updated due to changes in the Cargo.toml - file, for example a new dependency is added, Cargo will exit with an - error. + 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: - It may be used in environments where you want to assert that the - Cargo.lock file is up-to-date (such as a CI build). + o The lock file is missing. + + o 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 diff --git a/src/doc/man/includes/options-locked.md b/src/doc/man/includes/options-locked.md index 34fa96bef..31c8d1e00 100644 --- a/src/doc/man/includes/options-locked.md +++ b/src/doc/man/includes/options-locked.md @@ -1,10 +1,13 @@ {{#option "`--locked`"}} -Requires the `Cargo.lock` file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the `Cargo.toml` file, for example -a new dependency is added, Cargo will exit with an error. +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: -It may be used in environments where you want to assert that the `Cargo.lock` -file is up-to-date (such as a CI build). +* 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. {{/option}} {{#option "`--offline`"}} diff --git a/src/doc/src/commands/cargo-add.md b/src/doc/src/commands/cargo-add.md index 15b461ab1..80fb05615 100644 --- a/src/doc/src/commands/cargo-add.md +++ b/src/doc/src/commands/cargo-add.md @@ -192,11 +192,15 @@ terminal.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-bench.md b/src/doc/src/commands/cargo-bench.md index 40ee4fd1b..45b26f2aa 100644 --- a/src/doc/src/commands/cargo-bench.md +++ b/src/doc/src/commands/cargo-bench.md @@ -378,11 +378,15 @@ coming from rustc are still emitted. Cannot be used with human or <
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-build.md b/src/doc/src/commands/cargo-build.md index 85cc12a18..83296999f 100644 --- a/src/doc/src/commands/cargo-build.md +++ b/src/doc/src/commands/cargo-build.md @@ -309,11 +309,15 @@ See https://github.com/
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-check.md b/src/doc/src/commands/cargo-check.md index 8ef1a28df..b8c991d57 100644 --- a/src/doc/src/commands/cargo-check.md +++ b/src/doc/src/commands/cargo-check.md @@ -291,11 +291,15 @@ coming from rustc are still emitted. Cannot be used with human or <
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-clean.md b/src/doc/src/commands/cargo-clean.md index fbcc783a0..aa4e0eb46 100644 --- a/src/doc/src/commands/cargo-clean.md +++ b/src/doc/src/commands/cargo-clean.md @@ -111,11 +111,15 @@ terminal.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-doc.md b/src/doc/src/commands/cargo-doc.md index a15c5a2ca..0c49b9e7a 100644 --- a/src/doc/src/commands/cargo-doc.md +++ b/src/doc/src/commands/cargo-doc.md @@ -266,11 +266,15 @@ coming from rustc are still emitted. Cannot be used with human or <
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-fetch.md b/src/doc/src/commands/cargo-fetch.md index 07a2b27de..694a4a2f0 100644 --- a/src/doc/src/commands/cargo-fetch.md +++ b/src/doc/src/commands/cargo-fetch.md @@ -80,11 +80,15 @@ terminal.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-fix.md b/src/doc/src/commands/cargo-fix.md index 3ea28ff05..7c78b6b89 100644 --- a/src/doc/src/commands/cargo-fix.md +++ b/src/doc/src/commands/cargo-fix.md @@ -371,11 +371,15 @@ coming from rustc are still emitted. Cannot be used with human or <
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-generate-lockfile.md b/src/doc/src/commands/cargo-generate-lockfile.md index df20604f0..ee52d544c 100644 --- a/src/doc/src/commands/cargo-generate-lockfile.md +++ b/src/doc/src/commands/cargo-generate-lockfile.md @@ -59,11 +59,15 @@ terminal.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-install.md b/src/doc/src/commands/cargo-install.md index 2629c8df9..d664bc7ed 100644 --- a/src/doc/src/commands/cargo-install.md +++ b/src/doc/src/commands/cargo-install.md @@ -267,11 +267,15 @@ information about timing information.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-metadata.md b/src/doc/src/commands/cargo-metadata.md index ebe3f990e..31c01df85 100644 --- a/src/doc/src/commands/cargo-metadata.md +++ b/src/doc/src/commands/cargo-metadata.md @@ -429,11 +429,15 @@ terminal.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-package.md b/src/doc/src/commands/cargo-package.md index ee36ff329..94fd89bd6 100644 --- a/src/doc/src/commands/cargo-package.md +++ b/src/doc/src/commands/cargo-package.md @@ -183,11 +183,15 @@ be specified multiple times, which enables all specified features.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-pkgid.md b/src/doc/src/commands/cargo-pkgid.md index 04fbbb2a5..e392985f1 100644 --- a/src/doc/src/commands/cargo-pkgid.md +++ b/src/doc/src/commands/cargo-pkgid.md @@ -91,11 +91,15 @@ terminal.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-publish.md b/src/doc/src/commands/cargo-publish.md index 8aecf270c..17d917b7c 100644 --- a/src/doc/src/commands/cargo-publish.md +++ b/src/doc/src/commands/cargo-publish.md @@ -152,11 +152,15 @@ be specified multiple times, which enables all specified features.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-remove.md b/src/doc/src/commands/cargo-remove.md index fd000e22a..afbcbf590 100644 --- a/src/doc/src/commands/cargo-remove.md +++ b/src/doc/src/commands/cargo-remove.md @@ -82,11 +82,15 @@ terminal.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-run.md b/src/doc/src/commands/cargo-run.md index 57b365191..cebd0edb2 100644 --- a/src/doc/src/commands/cargo-run.md +++ b/src/doc/src/commands/cargo-run.md @@ -211,11 +211,15 @@ coming from rustc are still emitted. Cannot be used with human or <
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-rustc.md b/src/doc/src/commands/cargo-rustc.md index 772632c46..3d72c5b2b 100644 --- a/src/doc/src/commands/cargo-rustc.md +++ b/src/doc/src/commands/cargo-rustc.md @@ -305,11 +305,15 @@ coming from rustc are still emitted. Cannot be used with human or <
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-rustdoc.md b/src/doc/src/commands/cargo-rustdoc.md index 574787b3c..d6faf986e 100644 --- a/src/doc/src/commands/cargo-rustdoc.md +++ b/src/doc/src/commands/cargo-rustdoc.md @@ -286,11 +286,15 @@ coming from rustc are still emitted. Cannot be used with human or <
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-test.md b/src/doc/src/commands/cargo-test.md index 6815b2f43..f631e9d45 100644 --- a/src/doc/src/commands/cargo-test.md +++ b/src/doc/src/commands/cargo-test.md @@ -407,11 +407,15 @@ coming from rustc are still emitted. Cannot be used with human or <
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-tree.md b/src/doc/src/commands/cargo-tree.md index 78c6a9d4d..a596a9b98 100644 --- a/src/doc/src/commands/cargo-tree.md +++ b/src/doc/src/commands/cargo-tree.md @@ -223,11 +223,15 @@ single quotes or double quotes around each pattern.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-update.md b/src/doc/src/commands/cargo-update.md index f20a48df4..6416c8149 100644 --- a/src/doc/src/commands/cargo-update.md +++ b/src/doc/src/commands/cargo-update.md @@ -100,11 +100,15 @@ terminal.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-vendor.md b/src/doc/src/commands/cargo-vendor.md index d3e029e8f..12269570b 100644 --- a/src/doc/src/commands/cargo-vendor.md +++ b/src/doc/src/commands/cargo-vendor.md @@ -69,11 +69,15 @@ only a subset of the packages have changed.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/doc/src/commands/cargo-verify-project.md b/src/doc/src/commands/cargo-verify-project.md index f9f135dfb..68bd00344 100644 --- a/src/doc/src/commands/cargo-verify-project.md +++ b/src/doc/src/commands/cargo-verify-project.md @@ -64,11 +64,15 @@ terminal.
--locked
-
Requires the Cargo.lock file be up-to-date. If the lock file is missing, -or it needs to be updated due to changes in the Cargo.toml file, for example -a new dependency is added, Cargo will exit with an error.

-

It may be used in environments where you want to assert that the Cargo.lock -file is up-to-date (such as a CI build).

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

--offline
diff --git a/src/etc/man/cargo-add.1 b/src/etc/man/cargo-add.1 index 7632b295d..49cd2fba9 100644 --- a/src/etc/man/cargo-add.1 +++ b/src/etc/man/cargo-add.1 @@ -223,12 +223,20 @@ Add dependencies to only the specified package. .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-bench.1 b/src/etc/man/cargo-bench.1 index b43e8f741..a307f8c8c 100644 --- a/src/etc/man/cargo-bench.1 +++ b/src/etc/man/cargo-bench.1 @@ -419,12 +419,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-build.1 b/src/etc/man/cargo-build.1 index 6e51d3320..7046b7f3f 100644 --- a/src/etc/man/cargo-build.1 +++ b/src/etc/man/cargo-build.1 @@ -337,12 +337,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-check.1 b/src/etc/man/cargo-check.1 index be0adf163..40207103b 100644 --- a/src/etc/man/cargo-check.1 +++ b/src/etc/man/cargo-check.1 @@ -318,12 +318,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-clean.1 b/src/etc/man/cargo-clean.1 index ddb1e7253..00f47ad91 100644 --- a/src/etc/man/cargo-clean.1 +++ b/src/etc/man/cargo-clean.1 @@ -117,12 +117,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-doc.1 b/src/etc/man/cargo-doc.1 index e449a6ba8..52ade6dae 100644 --- a/src/etc/man/cargo-doc.1 +++ b/src/etc/man/cargo-doc.1 @@ -285,12 +285,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-fetch.1 b/src/etc/man/cargo-fetch.1 index 323130c4d..6687506f4 100644 --- a/src/etc/man/cargo-fetch.1 +++ b/src/etc/man/cargo-fetch.1 @@ -85,12 +85,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-fix.1 b/src/etc/man/cargo-fix.1 index 0e3436d50..fbf933fd3 100644 --- a/src/etc/man/cargo-fix.1 +++ b/src/etc/man/cargo-fix.1 @@ -413,12 +413,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-generate-lockfile.1 b/src/etc/man/cargo-generate-lockfile.1 index 066357ea3..a436909f8 100644 --- a/src/etc/man/cargo-generate-lockfile.1 +++ b/src/etc/man/cargo-generate-lockfile.1 @@ -64,12 +64,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-install.1 b/src/etc/man/cargo-install.1 index e14be11a5..c59d54b01 100644 --- a/src/etc/man/cargo-install.1 +++ b/src/etc/man/cargo-install.1 @@ -304,12 +304,20 @@ information about timing information. .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-metadata.1 b/src/etc/man/cargo-metadata.1 index 60e99f9df..e3cc27732 100644 --- a/src/etc/man/cargo-metadata.1 +++ b/src/etc/man/cargo-metadata.1 @@ -438,12 +438,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-package.1 b/src/etc/man/cargo-package.1 index 81ed84da8..a6ab96cb6 100644 --- a/src/etc/man/cargo-package.1 +++ b/src/etc/man/cargo-package.1 @@ -200,12 +200,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-pkgid.1 b/src/etc/man/cargo-pkgid.1 index 6ac6a480b..f8b7724bd 100644 --- a/src/etc/man/cargo-pkgid.1 +++ b/src/etc/man/cargo-pkgid.1 @@ -123,12 +123,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-publish.1 b/src/etc/man/cargo-publish.1 index 57919c8dc..8a65416f7 100644 --- a/src/etc/man/cargo-publish.1 +++ b/src/etc/man/cargo-publish.1 @@ -156,12 +156,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-remove.1 b/src/etc/man/cargo-remove.1 index 1296a8bed..12f1dcfe8 100644 --- a/src/etc/man/cargo-remove.1 +++ b/src/etc/man/cargo-remove.1 @@ -83,12 +83,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-run.1 b/src/etc/man/cargo-run.1 index 451489c4c..8b3564049 100644 --- a/src/etc/man/cargo-run.1 +++ b/src/etc/man/cargo-run.1 @@ -222,12 +222,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-rustc.1 b/src/etc/man/cargo-rustc.1 index fb1b78ade..621db1e6e 100644 --- a/src/etc/man/cargo-rustc.1 +++ b/src/etc/man/cargo-rustc.1 @@ -336,12 +336,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-rustdoc.1 b/src/etc/man/cargo-rustdoc.1 index cec32b0e6..32bdb57d1 100644 --- a/src/etc/man/cargo-rustdoc.1 +++ b/src/etc/man/cargo-rustdoc.1 @@ -304,12 +304,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-test.1 b/src/etc/man/cargo-test.1 index e1b93f994..09a47068d 100644 --- a/src/etc/man/cargo-test.1 +++ b/src/etc/man/cargo-test.1 @@ -446,12 +446,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-tree.1 b/src/etc/man/cargo-tree.1 index 1cdf3397b..9c08491c8 100644 --- a/src/etc/man/cargo-tree.1 +++ b/src/etc/man/cargo-tree.1 @@ -268,12 +268,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-update.1 b/src/etc/man/cargo-update.1 index 78550378c..daad6db8a 100644 --- a/src/etc/man/cargo-update.1 +++ b/src/etc/man/cargo-update.1 @@ -107,12 +107,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-vendor.1 b/src/etc/man/cargo-vendor.1 index bc1de2f71..b739f2c8f 100644 --- a/src/etc/man/cargo-vendor.1 +++ b/src/etc/man/cargo-vendor.1 @@ -64,12 +64,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/src/etc/man/cargo-verify-project.1 b/src/etc/man/cargo-verify-project.1 index 657ca5f2b..b0e6d8c7c 100644 --- a/src/etc/man/cargo-verify-project.1 +++ b/src/etc/man/cargo-verify-project.1 @@ -74,12 +74,20 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the .sp \fB\-\-locked\fR .RS 4 -Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing, -or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example -a new dependency is added, Cargo will exit with an error. +Asserts that the exact same dependencies and versions are used as when the +existing \fBCargo.lock\fR file was originally generated. Cargo will exit with an +error when either of the following scenarios arises: .sp -It may be used in environments where you want to assert that the \fBCargo.lock\fR -file is up\-to\-date (such as a CI build). +.RS 4 +\h'-04'\(bu\h'+02'The lock file is missing. +.RE +.sp +.RS 4 +\h'-04'\(bu\h'+02'Cargo attempted to change the lock file due to a different dependency resolution. +.RE +.sp +It may be used in environments where deterministic builds are desired, +such as in CI pipelines. .RE .sp \fB\-\-offline\fR diff --git a/tests/testsuite/cargo/help/stdout.term.svg b/tests/testsuite/cargo/help/stdout.term.svg index 0b087a574..19d2cee54 100644 --- a/tests/testsuite/cargo/help/stdout.term.svg +++ b/tests/testsuite/cargo/help/stdout.term.svg @@ -45,7 +45,7 @@ -C <DIRECTORY> Change to DIRECTORY before doing anything (nightly-only) - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_add/help/stdout.term.svg b/tests/testsuite/cargo_add/help/stdout.term.svg index 0d86a19d8..729a83c6c 100644 --- a/tests/testsuite/cargo_add/help/stdout.term.svg +++ b/tests/testsuite/cargo_add/help/stdout.term.svg @@ -181,7 +181,7 @@ --locked - Require Cargo.lock to be up-to-date + Assert that `Cargo.lock` will remain unchanged diff --git a/tests/testsuite/cargo_bench/help/stdout.term.svg b/tests/testsuite/cargo_bench/help/stdout.term.svg index 029db745a..2fe6694e8 100644 --- a/tests/testsuite/cargo_bench/help/stdout.term.svg +++ b/tests/testsuite/cargo_bench/help/stdout.term.svg @@ -127,7 +127,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_build/help/stdout.term.svg b/tests/testsuite/cargo_build/help/stdout.term.svg index 6cc51e692..848700357 100644 --- a/tests/testsuite/cargo_build/help/stdout.term.svg +++ b/tests/testsuite/cargo_build/help/stdout.term.svg @@ -125,7 +125,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_check/help/stdout.term.svg b/tests/testsuite/cargo_check/help/stdout.term.svg index df573a987..7f145892b 100644 --- a/tests/testsuite/cargo_check/help/stdout.term.svg +++ b/tests/testsuite/cargo_check/help/stdout.term.svg @@ -121,7 +121,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_clean/help/stdout.term.svg b/tests/testsuite/cargo_clean/help/stdout.term.svg index f2c6ef2ef..125fdd4c7 100644 --- a/tests/testsuite/cargo_clean/help/stdout.term.svg +++ b/tests/testsuite/cargo_clean/help/stdout.term.svg @@ -69,7 +69,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_config/help/stdout.term.svg b/tests/testsuite/cargo_config/help/stdout.term.svg index e57c40e27..184a739c7 100644 --- a/tests/testsuite/cargo_config/help/stdout.term.svg +++ b/tests/testsuite/cargo_config/help/stdout.term.svg @@ -51,7 +51,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_doc/help/stdout.term.svg b/tests/testsuite/cargo_doc/help/stdout.term.svg index 625889aff..7c3433c9e 100644 --- a/tests/testsuite/cargo_doc/help/stdout.term.svg +++ b/tests/testsuite/cargo_doc/help/stdout.term.svg @@ -115,7 +115,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_fetch/help/stdout.term.svg b/tests/testsuite/cargo_fetch/help/stdout.term.svg index 26e762e8f..78c9dcc69 100644 --- a/tests/testsuite/cargo_fetch/help/stdout.term.svg +++ b/tests/testsuite/cargo_fetch/help/stdout.term.svg @@ -53,7 +53,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_fix/help/stdout.term.svg b/tests/testsuite/cargo_fix/help/stdout.term.svg index 7a2286fc6..f4b05252f 100644 --- a/tests/testsuite/cargo_fix/help/stdout.term.svg +++ b/tests/testsuite/cargo_fix/help/stdout.term.svg @@ -129,7 +129,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_generate_lockfile/help/stdout.term.svg b/tests/testsuite/cargo_generate_lockfile/help/stdout.term.svg index 98f5fae89..80de855fa 100644 --- a/tests/testsuite/cargo_generate_lockfile/help/stdout.term.svg +++ b/tests/testsuite/cargo_generate_lockfile/help/stdout.term.svg @@ -47,7 +47,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_help/help/stdout.term.svg b/tests/testsuite/cargo_help/help/stdout.term.svg index 251fcef43..e63595e20 100644 --- a/tests/testsuite/cargo_help/help/stdout.term.svg +++ b/tests/testsuite/cargo_help/help/stdout.term.svg @@ -51,7 +51,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_init/help/stdout.term.svg b/tests/testsuite/cargo_init/help/stdout.term.svg index 7080cf488..fdfabe6e7 100644 --- a/tests/testsuite/cargo_init/help/stdout.term.svg +++ b/tests/testsuite/cargo_init/help/stdout.term.svg @@ -69,7 +69,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_install/help/stdout.term.svg b/tests/testsuite/cargo_install/help/stdout.term.svg index d226bdc3b..0e1a81c75 100644 --- a/tests/testsuite/cargo_install/help/stdout.term.svg +++ b/tests/testsuite/cargo_install/help/stdout.term.svg @@ -121,7 +121,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_locate_project/help/stdout.term.svg b/tests/testsuite/cargo_locate_project/help/stdout.term.svg index 70b305a84..2282c274e 100644 --- a/tests/testsuite/cargo_locate_project/help/stdout.term.svg +++ b/tests/testsuite/cargo_locate_project/help/stdout.term.svg @@ -53,7 +53,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_login/help/stdout.term.svg b/tests/testsuite/cargo_login/help/stdout.term.svg index 51be04e82..d6b62219b 100644 --- a/tests/testsuite/cargo_login/help/stdout.term.svg +++ b/tests/testsuite/cargo_login/help/stdout.term.svg @@ -55,7 +55,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_logout/help/stdout.term.svg b/tests/testsuite/cargo_logout/help/stdout.term.svg index f8750437e..2b390fe99 100644 --- a/tests/testsuite/cargo_logout/help/stdout.term.svg +++ b/tests/testsuite/cargo_logout/help/stdout.term.svg @@ -47,7 +47,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_metadata/help/stdout.term.svg b/tests/testsuite/cargo_metadata/help/stdout.term.svg index 43a082c29..6c6196be4 100644 --- a/tests/testsuite/cargo_metadata/help/stdout.term.svg +++ b/tests/testsuite/cargo_metadata/help/stdout.term.svg @@ -69,7 +69,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_new/help/stdout.term.svg b/tests/testsuite/cargo_new/help/stdout.term.svg index d6f12aafa..c7819a1c7 100644 --- a/tests/testsuite/cargo_new/help/stdout.term.svg +++ b/tests/testsuite/cargo_new/help/stdout.term.svg @@ -69,7 +69,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_owner/help/stdout.term.svg b/tests/testsuite/cargo_owner/help/stdout.term.svg index 4d040bcad..ed0adcc6c 100644 --- a/tests/testsuite/cargo_owner/help/stdout.term.svg +++ b/tests/testsuite/cargo_owner/help/stdout.term.svg @@ -63,7 +63,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_package/help/stdout.term.svg b/tests/testsuite/cargo_package/help/stdout.term.svg index 5d0a0decf..0b341bc22 100644 --- a/tests/testsuite/cargo_package/help/stdout.term.svg +++ b/tests/testsuite/cargo_package/help/stdout.term.svg @@ -87,7 +87,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_pkgid/help/stdout.term.svg b/tests/testsuite/cargo_pkgid/help/stdout.term.svg index 3e7d985cf..3efa36f6f 100644 --- a/tests/testsuite/cargo_pkgid/help/stdout.term.svg +++ b/tests/testsuite/cargo_pkgid/help/stdout.term.svg @@ -59,7 +59,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_publish/help/stdout.term.svg b/tests/testsuite/cargo_publish/help/stdout.term.svg index 240bb9ee1..671bd5c96 100644 --- a/tests/testsuite/cargo_publish/help/stdout.term.svg +++ b/tests/testsuite/cargo_publish/help/stdout.term.svg @@ -87,7 +87,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_read_manifest/help/stdout.term.svg b/tests/testsuite/cargo_read_manifest/help/stdout.term.svg index f81c9a268..b636b69f6 100644 --- a/tests/testsuite/cargo_read_manifest/help/stdout.term.svg +++ b/tests/testsuite/cargo_read_manifest/help/stdout.term.svg @@ -51,7 +51,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_remove/help/stdout.term.svg b/tests/testsuite/cargo_remove/help/stdout.term.svg index cbaab26ce..7e6ee2832 100644 --- a/tests/testsuite/cargo_remove/help/stdout.term.svg +++ b/tests/testsuite/cargo_remove/help/stdout.term.svg @@ -71,7 +71,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_report/help/stdout.term.svg b/tests/testsuite/cargo_report/help/stdout.term.svg index 2df6b7d33..477a51a7c 100644 --- a/tests/testsuite/cargo_report/help/stdout.term.svg +++ b/tests/testsuite/cargo_report/help/stdout.term.svg @@ -51,7 +51,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_run/help/stdout.term.svg b/tests/testsuite/cargo_run/help/stdout.term.svg index 916e047c3..e459231d7 100644 --- a/tests/testsuite/cargo_run/help/stdout.term.svg +++ b/tests/testsuite/cargo_run/help/stdout.term.svg @@ -103,7 +103,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_rustc/help/stdout.term.svg b/tests/testsuite/cargo_rustc/help/stdout.term.svg index 0c8f49179..e6e97c399 100644 --- a/tests/testsuite/cargo_rustc/help/stdout.term.svg +++ b/tests/testsuite/cargo_rustc/help/stdout.term.svg @@ -125,7 +125,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_rustdoc/help/stdout.term.svg b/tests/testsuite/cargo_rustdoc/help/stdout.term.svg index 9b31646bf..3d5bbbbfa 100644 --- a/tests/testsuite/cargo_rustdoc/help/stdout.term.svg +++ b/tests/testsuite/cargo_rustdoc/help/stdout.term.svg @@ -123,7 +123,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_search/help/stdout.term.svg b/tests/testsuite/cargo_search/help/stdout.term.svg index 9884ffa31..2824777d1 100644 --- a/tests/testsuite/cargo_search/help/stdout.term.svg +++ b/tests/testsuite/cargo_search/help/stdout.term.svg @@ -57,7 +57,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_test/help/stdout.term.svg b/tests/testsuite/cargo_test/help/stdout.term.svg index 994387fc0..0ec4686cd 100644 --- a/tests/testsuite/cargo_test/help/stdout.term.svg +++ b/tests/testsuite/cargo_test/help/stdout.term.svg @@ -133,7 +133,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_tree/help/stdout.term.svg b/tests/testsuite/cargo_tree/help/stdout.term.svg index 57568a0bd..7e87db4d5 100644 --- a/tests/testsuite/cargo_tree/help/stdout.term.svg +++ b/tests/testsuite/cargo_tree/help/stdout.term.svg @@ -97,7 +97,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_uninstall/help/stdout.term.svg b/tests/testsuite/cargo_uninstall/help/stdout.term.svg index 4eb4f3a9a..be47dba36 100644 --- a/tests/testsuite/cargo_uninstall/help/stdout.term.svg +++ b/tests/testsuite/cargo_uninstall/help/stdout.term.svg @@ -65,7 +65,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_update/help/stdout.term.svg b/tests/testsuite/cargo_update/help/stdout.term.svg index 46285c95d..f069ae4de 100644 --- a/tests/testsuite/cargo_update/help/stdout.term.svg +++ b/tests/testsuite/cargo_update/help/stdout.term.svg @@ -61,7 +61,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_vendor/help/stdout.term.svg b/tests/testsuite/cargo_vendor/help/stdout.term.svg index 9b1fe4aea..3481541c7 100644 --- a/tests/testsuite/cargo_vendor/help/stdout.term.svg +++ b/tests/testsuite/cargo_vendor/help/stdout.term.svg @@ -63,7 +63,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_verify_project/help/stdout.term.svg b/tests/testsuite/cargo_verify_project/help/stdout.term.svg index d36c74030..8d537a83d 100644 --- a/tests/testsuite/cargo_verify_project/help/stdout.term.svg +++ b/tests/testsuite/cargo_verify_project/help/stdout.term.svg @@ -47,7 +47,7 @@ --manifest-path <PATH> Path to Cargo.toml - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_version/help/stdout.term.svg b/tests/testsuite/cargo_version/help/stdout.term.svg index ee3ffa43f..548214725 100644 --- a/tests/testsuite/cargo_version/help/stdout.term.svg +++ b/tests/testsuite/cargo_version/help/stdout.term.svg @@ -45,7 +45,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network diff --git a/tests/testsuite/cargo_yank/help/stdout.term.svg b/tests/testsuite/cargo_yank/help/stdout.term.svg index c378d4d00..7a71b49e1 100644 --- a/tests/testsuite/cargo_yank/help/stdout.term.svg +++ b/tests/testsuite/cargo_yank/help/stdout.term.svg @@ -61,7 +61,7 @@ Manifest Options: - --locked Require Cargo.lock to be up-to-date + --locked Assert that `Cargo.lock` will remain unchanged --offline Run without accessing the network