chore: update uv pip package 0.10.3 → 0.11.2 in lock file#1501
Merged
chore: update uv pip package 0.10.3 → 0.11.2 in lock file#1501
Conversation
The tox-uv plugin installs the uv pip package into .venv/bin/uv. Version 0.10.3 has a different managed-Python discovery directory than uv >=0.11 (installed by setup-uv in CI), causing tox to skip py312/py313 envs with "could not find python interpreter". Aligns with the existing required-version = "~=0.11.0" constraint.
jaceksan
approved these changes
Mar 31, 2026
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.
Summary
uvpip package from 0.10.3 to 0.11.2 inuv.lockrequired-version = "~=0.11.0"constraint inpyproject.tomlWhy: tox-uv installs the
uvpip package into.venv/bin/uv. Version 0.10.3 has a different managed-Python discovery directory than uv >=0.11 (installed bysetup-uvin CI), causing tox to skippy312/py313envs with "could not find python interpreter". This one-line lock update fixes it.