docs: clarify --locked disallows changes in Cargo.lock

src/bin/cargo/cli.rs

@@ -640,7 +640,7 @@ See '<cyan,bold>cargo help</> <cyan><<command>></>' 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),
         )

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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`"}}

src/doc/src/commands/cargo-add.md

@@ -192,11 +192,15 @@ terminal.</li>
 
 
 <dt class="option-term" id="option-cargo-add---locked"><a class="option-anchor" href="#option-cargo-add---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-add---offline"><a class="option-anchor" href="#option-cargo-add---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-bench.md

@@ -378,11 +378,15 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
 
 
 <dt class="option-term" id="option-cargo-bench---locked"><a class="option-anchor" href="#option-cargo-bench---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-bench---offline"><a class="option-anchor" href="#option-cargo-bench---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-build.md

@@ -309,11 +309,15 @@ See <a href="https://github.com/rust-lang/cargo/issues/5579">https://github.com/
 
 
 <dt class="option-term" id="option-cargo-build---locked"><a class="option-anchor" href="#option-cargo-build---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-build---offline"><a class="option-anchor" href="#option-cargo-build---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-check.md

@@ -291,11 +291,15 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
 
 
 <dt class="option-term" id="option-cargo-check---locked"><a class="option-anchor" href="#option-cargo-check---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-check---offline"><a class="option-anchor" href="#option-cargo-check---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-clean.md

@@ -111,11 +111,15 @@ terminal.</li>
 
 
 <dt class="option-term" id="option-cargo-clean---locked"><a class="option-anchor" href="#option-cargo-clean---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-clean---offline"><a class="option-anchor" href="#option-cargo-clean---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-doc.md

@@ -266,11 +266,15 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
 
 
 <dt class="option-term" id="option-cargo-doc---locked"><a class="option-anchor" href="#option-cargo-doc---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-doc---offline"><a class="option-anchor" href="#option-cargo-doc---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-fetch.md

@@ -80,11 +80,15 @@ terminal.</li>
 
 
 <dt class="option-term" id="option-cargo-fetch---locked"><a class="option-anchor" href="#option-cargo-fetch---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-fetch---offline"><a class="option-anchor" href="#option-cargo-fetch---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-fix.md

@@ -371,11 +371,15 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
 
 
 <dt class="option-term" id="option-cargo-fix---locked"><a class="option-anchor" href="#option-cargo-fix---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-fix---offline"><a class="option-anchor" href="#option-cargo-fix---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-generate-lockfile.md

@@ -59,11 +59,15 @@ terminal.</li>
 
 
 <dt class="option-term" id="option-cargo-generate-lockfile---locked"><a class="option-anchor" href="#option-cargo-generate-lockfile---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-generate-lockfile---offline"><a class="option-anchor" href="#option-cargo-generate-lockfile---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-install.md

@@ -267,11 +267,15 @@ information about timing information.</li>
 
 <dl>
 <dt class="option-term" id="option-cargo-install---locked"><a class="option-anchor" href="#option-cargo-install---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-install---offline"><a class="option-anchor" href="#option-cargo-install---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-metadata.md

@@ -429,11 +429,15 @@ terminal.</li>
 
 
 <dt class="option-term" id="option-cargo-metadata---locked"><a class="option-anchor" href="#option-cargo-metadata---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-metadata---offline"><a class="option-anchor" href="#option-cargo-metadata---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-package.md

@@ -183,11 +183,15 @@ be specified multiple times, which enables all specified features.</dd>
 
 
 <dt class="option-term" id="option-cargo-package---locked"><a class="option-anchor" href="#option-cargo-package---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-package---offline"><a class="option-anchor" href="#option-cargo-package---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-pkgid.md

@@ -91,11 +91,15 @@ terminal.</li>
 
 
 <dt class="option-term" id="option-cargo-pkgid---locked"><a class="option-anchor" href="#option-cargo-pkgid---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-pkgid---offline"><a class="option-anchor" href="#option-cargo-pkgid---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-publish.md

@@ -152,11 +152,15 @@ be specified multiple times, which enables all specified features.</dd>
 
 
 <dt class="option-term" id="option-cargo-publish---locked"><a class="option-anchor" href="#option-cargo-publish---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-publish---offline"><a class="option-anchor" href="#option-cargo-publish---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-remove.md

@@ -82,11 +82,15 @@ terminal.</li>
 
 
 <dt class="option-term" id="option-cargo-remove---locked"><a class="option-anchor" href="#option-cargo-remove---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-remove---offline"><a class="option-anchor" href="#option-cargo-remove---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-run.md

@@ -211,11 +211,15 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
 
 
 <dt class="option-term" id="option-cargo-run---locked"><a class="option-anchor" href="#option-cargo-run---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-run---offline"><a class="option-anchor" href="#option-cargo-run---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-rustc.md

@@ -305,11 +305,15 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
 
 
 <dt class="option-term" id="option-cargo-rustc---locked"><a class="option-anchor" href="#option-cargo-rustc---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-rustc---offline"><a class="option-anchor" href="#option-cargo-rustc---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-rustdoc.md

@@ -286,11 +286,15 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
 
 
 <dt class="option-term" id="option-cargo-rustdoc---locked"><a class="option-anchor" href="#option-cargo-rustdoc---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-rustdoc---offline"><a class="option-anchor" href="#option-cargo-rustdoc---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-test.md

@@ -407,11 +407,15 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
 
 
 <dt class="option-term" id="option-cargo-test---locked"><a class="option-anchor" href="#option-cargo-test---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-test---offline"><a class="option-anchor" href="#option-cargo-test---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-tree.md

@@ -223,11 +223,15 @@ single quotes or double quotes around each pattern.</dd>
 
 
 <dt class="option-term" id="option-cargo-tree---locked"><a class="option-anchor" href="#option-cargo-tree---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-tree---offline"><a class="option-anchor" href="#option-cargo-tree---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-update.md

@@ -100,11 +100,15 @@ terminal.</li>
 
 
 <dt class="option-term" id="option-cargo-update---locked"><a class="option-anchor" href="#option-cargo-update---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-update---offline"><a class="option-anchor" href="#option-cargo-update---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-vendor.md

@@ -69,11 +69,15 @@ only a subset of the packages have changed.</dd>
 
 
 <dt class="option-term" id="option-cargo-vendor---locked"><a class="option-anchor" href="#option-cargo-vendor---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-vendor---offline"><a class="option-anchor" href="#option-cargo-vendor---offline"></a><code>--offline</code></dt>

src/doc/src/commands/cargo-verify-project.md

@@ -64,11 +64,15 @@ terminal.</li>
 
 
 <dt class="option-term" id="option-cargo-verify-project---locked"><a class="option-anchor" href="#option-cargo-verify-project---locked"></a><code>--locked</code></dt>
-<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
-or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
-a new dependency is added, Cargo will exit with an error.</p>
-<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
-file is up-to-date (such as a CI build).</dd>
+<dd class="option-desc">Asserts that the exact same dependencies and versions are used as when the
+existing <code>Cargo.lock</code> file was originally generated. Cargo will exit with an
+error when either of the following scenarios arises:</p>
+<ul>
+<li>The lock file is missing.</li>
+<li>Cargo attempted to change the lock file due to a different dependency resolution.</li>
+</ul>
+<p>It may be used in environments where deterministic builds are desired,
+such as in CI pipelines.</dd>
 
 
 <dt class="option-term" id="option-cargo-verify-project---offline"><a class="option-anchor" href="#option-cargo-verify-project---offline"></a><code>--offline</code></dt>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

tests/testsuite/cargo/help/stdout.term.svg

@@ -45,7 +45,7 @@
 </tspan>
     <tspan x="10px" y="244px"><tspan>  </tspan><tspan class="fg-cyan bold">-C</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;DIRECTORY&gt;</tspan><tspan>            Change to DIRECTORY before doing anything (nightly-only)</tspan>
 </tspan>
-    <tspan x="10px" y="262px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>              Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="262px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>              Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="280px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>             Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_add/help/stdout.term.svg

@@ -181,7 +181,7 @@
 </tspan>
     <tspan x="10px" y="1468px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan>
 </tspan>
-    <tspan x="10px" y="1486px"><tspan>          Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="1486px"><tspan>          Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="1504px">
 </tspan>

tests/testsuite/cargo_bench/help/stdout.term.svg

@@ -127,7 +127,7 @@
 </tspan>
     <tspan x="10px" y="982px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="1000px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="1000px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="1018px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_build/help/stdout.term.svg

@@ -125,7 +125,7 @@
 </tspan>
     <tspan x="10px" y="964px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="982px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="982px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="1000px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_check/help/stdout.term.svg

@@ -121,7 +121,7 @@
 </tspan>
     <tspan x="10px" y="928px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="946px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="946px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="964px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_clean/help/stdout.term.svg

@@ -69,7 +69,7 @@
 </tspan>
     <tspan x="10px" y="460px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="478px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="478px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="496px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_config/help/stdout.term.svg

@@ -51,7 +51,7 @@
 </tspan>
     <tspan x="10px" y="298px"><tspan class="fg-green bold">Manifest Options:</tspan>
 </tspan>
-    <tspan x="10px" y="316px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="316px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="334px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>  Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_doc/help/stdout.term.svg

@@ -115,7 +115,7 @@
 </tspan>
     <tspan x="10px" y="874px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="892px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="892px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="910px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_fetch/help/stdout.term.svg

@@ -53,7 +53,7 @@
 </tspan>
     <tspan x="10px" y="316px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="334px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="334px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="352px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_fix/help/stdout.term.svg

@@ -129,7 +129,7 @@
 </tspan>
     <tspan x="10px" y="1000px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="1018px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="1018px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="1036px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_generate_lockfile/help/stdout.term.svg

@@ -47,7 +47,7 @@
 </tspan>
     <tspan x="10px" y="262px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="280px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="280px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="298px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_help/help/stdout.term.svg

@@ -51,7 +51,7 @@
 </tspan>
     <tspan x="10px" y="298px"><tspan class="fg-green bold">Manifest Options:</tspan>
 </tspan>
-    <tspan x="10px" y="316px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="316px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="334px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>  Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_init/help/stdout.term.svg

@@ -69,7 +69,7 @@
 </tspan>
     <tspan x="10px" y="460px"><tspan class="fg-green bold">Manifest Options:</tspan>
 </tspan>
-    <tspan x="10px" y="478px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="478px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="496px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>  Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_install/help/stdout.term.svg

@@ -121,7 +121,7 @@
 </tspan>
     <tspan x="10px" y="928px"><tspan class="fg-green bold">Manifest Options:</tspan>
 </tspan>
-    <tspan x="10px" y="946px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="946px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="964px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>  Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_locate_project/help/stdout.term.svg

@@ -53,7 +53,7 @@
 </tspan>
     <tspan x="10px" y="316px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="334px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="334px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="352px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_login/help/stdout.term.svg

@@ -55,7 +55,7 @@
 </tspan>
     <tspan x="10px" y="334px"><tspan class="fg-green bold">Manifest Options:</tspan>
 </tspan>
-    <tspan x="10px" y="352px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="352px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="370px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>  Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_logout/help/stdout.term.svg

@@ -47,7 +47,7 @@
 </tspan>
     <tspan x="10px" y="262px"><tspan class="fg-green bold">Manifest Options:</tspan>
 </tspan>
-    <tspan x="10px" y="280px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="280px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="298px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>  Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_metadata/help/stdout.term.svg

@@ -69,7 +69,7 @@
 </tspan>
     <tspan x="10px" y="460px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="478px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="478px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="496px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_new/help/stdout.term.svg

@@ -69,7 +69,7 @@
 </tspan>
     <tspan x="10px" y="460px"><tspan class="fg-green bold">Manifest Options:</tspan>
 </tspan>
-    <tspan x="10px" y="478px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="478px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="496px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>  Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_owner/help/stdout.term.svg

@@ -63,7 +63,7 @@
 </tspan>
     <tspan x="10px" y="406px"><tspan class="fg-green bold">Manifest Options:</tspan>
 </tspan>
-    <tspan x="10px" y="424px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="424px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="442px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>  Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_package/help/stdout.term.svg

@@ -87,7 +87,7 @@
 </tspan>
     <tspan x="10px" y="622px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="640px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="640px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="658px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_pkgid/help/stdout.term.svg

@@ -59,7 +59,7 @@
 </tspan>
     <tspan x="10px" y="370px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="388px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="388px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="406px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_publish/help/stdout.term.svg

@@ -87,7 +87,7 @@
 </tspan>
     <tspan x="10px" y="622px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="640px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="640px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="658px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_read_manifest/help/stdout.term.svg

@@ -51,7 +51,7 @@
 </tspan>
     <tspan x="10px" y="298px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="316px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="316px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="334px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_remove/help/stdout.term.svg

@@ -71,7 +71,7 @@
 </tspan>
     <tspan x="10px" y="478px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="496px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="496px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="514px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_report/help/stdout.term.svg

@@ -51,7 +51,7 @@
 </tspan>
     <tspan x="10px" y="298px"><tspan class="fg-green bold">Manifest Options:</tspan>
 </tspan>
-    <tspan x="10px" y="316px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="316px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>   Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="334px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>  Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_run/help/stdout.term.svg

@@ -103,7 +103,7 @@
 </tspan>
     <tspan x="10px" y="766px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="784px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="784px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="802px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_rustc/help/stdout.term.svg

@@ -125,7 +125,7 @@
 </tspan>
     <tspan x="10px" y="964px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="982px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="982px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="1000px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>

tests/testsuite/cargo_rustdoc/help/stdout.term.svg

@@ -123,7 +123,7 @@
 </tspan>
     <tspan x="10px" y="946px"><tspan>      </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan>  Path to Cargo.toml</tspan>
 </tspan>
-    <tspan x="10px" y="964px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Require Cargo.lock to be up-to-date</tspan>
+    <tspan x="10px" y="964px"><tspan>      </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan>                Assert that `Cargo.lock` will remain unchanged</tspan>
 </tspan>
     <tspan x="10px" y="982px"><tspan>      </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan>               Run without accessing the network</tspan>
 </tspan>