lockfileMaintenance ignores uv's resolution-mode

[stefanofusai]

How are you running Renovate?

A Mend.io-hosted app

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

As you can see in this PR, Renovate's lockfileMaintenance overwrites the resolution-mode that is set in uv.lock's options.

I would expect the custom options to be preserved, or for a way to specify which command lockfileMaintenance should run (in my case: uv lock -resolution=lowest-direct)

What approach do you suggest? Thank you!

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[rarkins]

Is there a definitive list of all such options which should be retained?

[stefanofusai]

I'm unfortunately not sure of all the available options, but IMO the more robust and future-proof solution would be to allow passing arbitrary arguments to the uv lock command, just like uv-pre-commit allows:

  - repo: https://github.com/astral-sh/uv-pre-commit
    rev: 0.5.11
    hooks:
      - id: uv-lock
        args:
          - --resolution=lowest-direct