uv.lock is not updated when using uv workspaces

[kkom]

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

When using the uv workspaces feature, Renovate-generated PRs do not update the workspace's uv.lock file.

Here's the layout of a typical uv project using workspaces:

albatross
├── packages
│   ├── bird-feeder
│   │   ├── pyproject.toml
│   │   └── src
│   │       └── bird_feeder
│   │           ├── __init__.py
│   │           └── foo.py
│   └── seeds
│       ├── pyproject.toml
│       └── src
│           └── seeds
│               ├── __init__.py
│               └── bar.py
├── pyproject.toml
├── README.md
├── uv.lock
└── src
    └── albatross
        └── main.py

Note how there is a single uv.lock file, but multiple pyproject.toml. Dependencies of member packages in a workspace are locked in the top-level uv.lock file, but Renovate fails to update it when bumping versions.

Perhaps Renovate isn't workspace-aware and assumes that each pyproject.toml should have a corresponding uv.lock file in the same directory?

AFAIK, the right solution is to run uv lock in the workspace root.

Logs (if relevant)

Logs

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

[github-actions[bot]]

Hi there,

Get your discussion fixed faster 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]

Please create a minimal reproduction so we can convey this into a feature request

[kkom]

Thanks! There you go: https://github.com/kkom/renovate-uv-workspaces-repro/pull/3/files

[rarkins]

Is there a deterministic way for Renovate to know which pyproject.toml files are associated with a particularly uv.lock?

[kkom]

@charliermarsh – would you be able to help @rarkins here?

[charliermarsh]

It would be (1) the pyproject.toml in the same directory, adjacent to the uv.lock; and (2) the pyproject.toml in every member directory enumerated by the [tool.uv.workspace] setting. It is roughly equivalent to Cargo's workspace model.

[rarkins]

Converted to issue: #33874