mirror of https://github.com/astral-sh/uv
225bffbb6c
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. |
||
|---|---|---|
| .. | ||
| .overrides | ||
| assets | ||
| concepts | ||
| getting-started | ||
| guides | ||
| js | ||
| pip | ||
| reference | ||
| stylesheets | ||
| .gitignore | ||
| index.md | ||
| requirements-insiders.in | ||
| requirements-insiders.txt | ||
| requirements.in | ||
| requirements.txt | ||