Indicate the version of uv that was used to generate/update the uv.lock file in the file itself

[sebn]

Summary

When starting a project with uv version 0.5.28, the uv.lock file would include something like this:

[[uv]]
version = 0.5.28

The value would be updated everytime a different uv binary version is used to change the lockfile, be it a newer version:

[[uv]]
version = 0.5.29

Or an older one:

[[uv]]
version = 0.5.27

Example

This would make it possible or at least easier to:

• Understand both for uv maintainers & uv users that some unexpected changes in the uv.lock file can be related to the version of the uv binary that was used & decide whether the change is legit or not.
• Display a warning in the console about the current version being used not matching the one in the lock file (separate feature, built on top of this one)
• Write a simple shell script in one's git repo that automatically install the uv version matching the one in their uv.lock file

[charliermarsh]

Hmm. I think this would be slightly problematic in that it would unnecessarily couple the lockfile to the uv version. For example, the lockfile would now be invalidated every time you update the uv version, despite the fact that the semantic contents may not change, and the lockfile itself is already versioned (and intended to be compatible with a wide range of uv versions).

I would suggest using required-version for this? It's intended for projects that want to enforce a specific uv version.