Support non-latest version of uv for lock update

[tanguylefloch-veesion]

Context

Currently renovate always uses the latest uv version to run uv commands.
However we pin the uv version following uv's config https://docs.astral.sh/uv/reference/settings/#required-version.

When trying to update the lock with an uv version which is not the required-version it breaks with:

error: Required uv version `==0.7.10` does not match the running version `0.7.11`. Update `uv` by running `uv self update 0.7.10`.

This is okayish right now as we update uv frequently, but will be more of an issue with future potential breaking changes.

Reproduction at https://github.com/tanguylefloch-veesion/renovate-repro-uv-version-detection

Suggestion

Use uv's required-version when present in the pyproject.toml

Alternative

Accept an uvVersion in renovate config

[github-actions[bot]]

Hi there,

Please help this Discussion progress by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running Renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team

[rarkins]

You should be able to work around this by manually configuring constraints.uv in your repo config. If you'd like Renovate to detect it automatically, we'll need a reproduction repo to work with (see instructions above)

[tanguylefloch-veesion]

Thanks for the swift reply @rarkins !

To clarify, the issue is not about updating uv itself (I managed that with a regex custom manager). It is about which version runs whenever renovate uses uv commands to update the uv lockfile. When renovate updates other packages.

I did the reproduction here https://github.com/tanguylefloch-veesion/renovate-repro-uv-version-detection

[rarkins]

Please read the docs for constraints and you'll understand my suggestion above better

[tanguylefloch-veesion]

I did, from what I understood:

1. uv.constraints would suit my use case (I'll try it) but that implies adding a separate source of truth for uv version in the repo. I guess I could have renovate update the renovate.json as well.
2. It should be in renovate's scope to detect uv's version as we are not in any of the cases described for constraints ("the package manager does not support specifying a constraint", "the project did not declare a constraint", "we want to declare a diff version that the project")

So I'll check it out but assumed the submission would still be helpful

[rarkins]

I assumed that you didn't understand the meaning of what I suggested because the entire paragraph you responded with was redundant

[rarkins]

I'll look at the reproduction later to see what's requires to automate the uv version detection (so config isn't necessary as a workaround)