Charles-Meldhine Madi Mnemoi 225bffbb6c Running `uv lock --check` with outdated lockfile will print that `--check` was passed, instead of `--locked` (#16322) ... Hello, # Summary This PR fixes the confusing error message when running `uv lock --check` with an outdated lockfile. Previously, the error message incorrectly stated that `--locked` was provided, even when the user used `--check`. Now, the error message correctly indicates which flag was used: either `--check` or `--locked`. This closes #14105. # Test plan - I updated the existing integration test (`check_outdated_lock` in `lock.rs`) to verify the new error message includes the correct flag. - I ran existing tests to ensure I have no introduced regressions for other commands.		2025-10-21 12:46:10 -05:00
..
internals	Document metadata consistency expectation (#15683)	2025-10-19 14:29:47 +02:00
policies	Windows arm64 and Linux RISC-V64 are Tier 2 supported (#16027)	2025-09-29 17:54:04 +02:00
troubleshooting	Fix and improve docs (#13620)	2025-06-10 13:15:38 -05:00
benchmarks.md	Add link to benchmarks in documentation (#6257)	2024-08-20 12:54:46 -04:00
cli.md	Running `uv lock --check` with outdated lockfile will print that `--check` was passed, instead of `--locked` (#16322)	2025-10-21 12:46:10 -05:00
environment.md	Missing added_in on new env vars (#16217)	2025-10-10 08:55:09 -05:00
index.md	Move Resolver to new Internals section in the Reference (#15465)	2025-08-22 19:26:16 -05:00
installer.md	Add `UV_` prefix to installer environment variables (#14964)	2025-07-30 01:24:59 +00:00
settings.md	Rename `provides_extras` to `provides_extra` (#15825)	2025-09-14 13:27:45 +00:00