The uv-lock hook updates uv.lock but does not commit it

[Adirelle]

I am not sure what the uv-lock is supposed to do:

• If it is supposed to check that the lockfile is up to date with regard to pyproject.toml, it should be run with the --locked to report any issue .
• If it is supposed to actually update the lockfile on commit, it should also automatically add the modified uv.lock to the git index so it gets included in the commit.

Right now it seems to be something in between: the lockfile is updated but not commited, and so it appears as a modified file after the commit has been done.

[thisiswhereitype]

I think this i pre-commit behaviour, failed commands and changes to tracked files indicate a failed hook.

This hook stops you committing an environment differing to the one you have uv sync.

[Adirelle]

Without --locked (the current settings of the hook), uv lock updates the lockfile with success so it does not stop committing.

With --locked, it does not update the file but fails, but could be more useful.

[thisiswhereitype]

Without --locked (the current settings of the hook), uv lock updates the lockfile with success so it does not stop committing.

In this case the changed file stops the commit?

[Adirelle]

Without --locked (the current settings of the hook), uv lock updates the lockfile with success so it does not stop committing.

In this case the changed file stops the commit?

IIRC it commited the unchanged file and left the modified file in the working tree.