Skip to content

Conversation

@Wetinee
Copy link

@Wetinee Wetinee commented Mar 26, 2025

Update backend Dockerfile to use the latest uv version.

Reasons

  1. I encountered an issue when building Docker images with the specific uv version (0.5.11). And switching to latest helped resolve the issue.

  2. 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.

@YuriiMotov YuriiMotov changed the title configure uv to use the latest version ♻️ Use the latest version of uv in backend/Dockerfile Sep 3, 2025
@stevleibelt
Copy link

uv is in high development mode. This could result in hard to reproduce issues when everyone could have a different latest version installed.

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 uv has reached version 1.0.x.

Thanks for the proposal @Wetinee

@github-actions github-actions bot added the conflicts Automatically generated when a PR has a merge conflict label Jan 21, 2026
@github-actions
Copy link
Contributor

This pull request has a merge conflict that needs to be resolved.

@tiangolo
Copy link
Member

Thanks! This was handled in another PR, so I'll close this one now. ☕

@tiangolo tiangolo closed this Jan 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

conflicts Automatically generated when a PR has a merge conflict refactor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants