Fix relative and absolute path handling in lockfiles#4266
Merged
BurntSushi merged 1 commit intomainfrom Jun 13, 2024
Merged
Conversation
BurntSushi
approved these changes
Jun 12, 2024
4584a70 to
b5d85f9
Compare
Previously, `b` would have been incorrectly locked to `a`.
b5d85f9 to
a645f6b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously,
bin the test case would have been incorrectly locked to the path ofa. I've movedrelative_tointo uv-fs since it's now used in two different places.Previously failing lockfile when
a/pyproject.tomlanda/b/pyproject.tomlexist (not in a workspace) andawas depending onb: