-
Notifications
You must be signed in to change notification settings - Fork 778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uv lock
collapses relative paths to editable builds in monorepo, breaks uv sync
#6371
Labels
bug
Something isn't working
Comments
Thanks, I'll take a look! |
Agree this is a bug, just reproduced. |
@konstin -- Do you mind taking a look at this in the morning? |
konstin
added a commit
that referenced
this issue
Aug 22, 2024
Pass the location of `uv.lock`, the base of our relative lockfile pass, through when locking in project mode. This fixes previous incorrect paths that were using the root of the other workspace as reference for the relative path. Fix #6371.
konstin
added a commit
that referenced
this issue
Aug 22, 2024
Pass the location of `uv.lock`, the base of our relative lockfile pass, through when locking in project mode. This fixes previous incorrect paths that were using the root of the other workspace as reference for the relative path. Fix #6371.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there! Excited to move our monorepo from poetry to uv.
There seems to be an issue with relative paths for editable installs in the lockfiles.
Using the following demo structure:
liba, libb, and projecta created with
uv init
libb depends on liba with an editable install
When locking libb with
uv lock
the path is resolved correctly, but also collapsed in the lockfileThis works fine since the path it correct.
However this does not work for projecta, which depends on libb:
uv lock produces this lockfile:
Where the collapsed relative path is still used for liba, which no longer works.
This makes
uv sync
fail:The text was updated successfully, but these errors were encountered: