-
Notifications
You must be signed in to change notification settings - Fork 995
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
Rename dev dependencies to dependency groups in lockfile #8391
Conversation
08317a1
to
189b040
Compare
How is this about forward compatibility? i.e. user who has old uv wants to interact with new lockfile from random project? |
bb83978
to
c246fbf
Compare
189b040
to
166f81a
Compare
Yeah this wouldn't work. I don't think bumping the version even helps here, because prior versions of uv don't look at it and don't (e.g.) throw an error or show a warning. |
## Summary This is backwards compatible (we respect `dev-dependencies` as an alias). Part of #8272.
## Summary This is backwards compatible (we respect `dev-dependencies` as an alias). Part of #8272.
…8501) ## Summary Per discussion on Discord, we're going to keep these names for now (changed in #8391 but not yet released) for compatibility. They're just cosmetic, but with the changes as-is, if you ran an older uv version over a newer lockfile... - For `uv sync`: the lockfile would be invalidated, and we'd re-resolve. - For `uv sync --frozen`: we'd silently skip the development dependencies. We'll change these names in the future once we've added better error handling around lockfile versions (#8465).
This is backwards compatible (we respect `dev-dependencies` as an alias). Part of #8272.
This is backwards compatible (we respect `dev-dependencies` as an alias). Part of #8272.
This is backwards compatible (we respect `dev-dependencies` as an alias). Part of #8272.
This is backwards compatible (we respect `dev-dependencies` as an alias). Part of #8272.
Summary
This is backwards compatible (we respect
dev-dependencies
as an alias).Part of #8272.