Don't use UV_LOCKED to enable --check flag (#16521)

Env var UV_LOCKED should only be used to enable `--locked` for the `uv
lock` command. Previously `--check` was also enabled by specifying
UV_LOCKED.
This commit is contained in:
Alexander Vandenbulcke
2025-10-30 20:37:27 +01:00
committed by GitHub
parent a1610c794e
commit c156b1d50d
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -3733,7 +3733,7 @@ pub struct LockArgs {
/// missing or needs to be updated, uv will exit with an error.
///
/// Equivalent to `--locked`.
#[arg(long, env = EnvVars::UV_LOCKED, value_parser = clap::builder::BoolishValueParser::new(), conflicts_with_all = ["check_exists", "upgrade", "locked"])]
#[arg(long, value_parser = clap::builder::BoolishValueParser::new(), conflicts_with_all = ["check_exists", "upgrade", "locked"])]
pub check: bool,
/// Check if the lockfile is up-to-date.