♻️ Use the latest version of uv in backend/Dockerfile
#1529
Conversation
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
YuriiMotov
changed the title
backend/Dockerfile
|
On the other hand, even not labeled as version 1.x, I am using uv in production already at it feels pretty mature in the sense of "I haven't encountered many cli/api changes since first use". I vote for 👍 until Thanks for the proposal @Wetinee |
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.
Update backend Dockerfile to use the latest uv version.
Reasons
I encountered an issue when building Docker images with the specific uv version (0.5.11). And switching to latest helped resolve the issue.
Using latest ensures that we don’t have to manually update the version in the future. This approach aligns with the recommendations in the uv documentation.