feat: upgrade uv to 0.5.29 #3075
Merged
Conversation
This file contains 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.
This PR upgrades the uv version to
0.5.29. There have been some internal API changes, so I had to adapt to that mainly. But I believe most behavior should stay the same.The biggest changes:
SharedState, this should solve the problem of us having to maintain a seperateInMemoryIndexas there is now a fork method. We can also look at sharing aGitResolver, between the solve and the install.BuildDispatchnow has his own error methods, which helped us to be able to get rid of anyhow.Preparerwhich is the downloader and builder, during instalation now requires aResolution, which helps with error derivations, which we do not always have in the installation. uv can also compute this from the lock but its a bit intense of a procedure to replicate for our lock-file, so I've just been using the default there.Testing
I hope in this case CI will cover most of the things :)