This is actually covered by the --locked option that uv sync provides. If you do `uv sync --locked` it will not succeed if the lock file does not exist or is o

This is actually covered by the --locked option that uv sync provides. If you do `uv sync --locked` it will not succeed if the lock file does not exist or is out of date. Edit: I slightly misread your comment. I strongly agree that having no lock file or a lockfile that does not match your specified dependencies is a case where a human should intervene. That's why I suggest you should always use the --locked option in your build.