uv.lock
is not updated when using uv
workspaces
#33275
Replies: 2 comments 1 reply
-
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:
If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide. The Renovate team |
Beta Was this translation helpful? Give feedback.
-
Please create a minimal reproduction so we can convey this into a feature request |
Beta Was this translation helpful? Give feedback.
-
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'suv.lock
file.Here's the layout of a typical
uv
project using workspaces:Note how there is a single
uv.lock
file, but multiplepyproject.toml
. Dependencies of member packages in a workspace are locked in the top-leveluv.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 correspondinguv.lock
file in the same directory?AFAIK, the right solution is to run
uv lock
in the workspace root.Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions