alt Hacker News> The parent's description isn't what happens with the original code
Yes, it is: both gchamonlive and myself pointed out that if your lock file exists and is out of date, your (previous) script would silently update it before installing. This would happen because `uv lock --check` would return false, triggering the call to `uv lock`.
Your new version no longer does that, because you removed `! uv lock --check` from the condition.
> Yes, it is: both gchamonlive and myself pointed out that if your lock file exists and is out of date, your (previous) script would silently update it before installing
Check my original comment, it doesn't operate like this. You can try it yourself in the same way I outlined in the comment.
`uv lock` fails if your lock file has a mismatch and will produce a human readable error saying what's wrong.