Repository navigation
Require uv >= 0.13.4 - #17464
Merged
Merged
Require uv >= 0.13.4#17464
Conversation
Matches the uv image pinned in the Dockerfile. uv uses its own embedded CA roots when talking to PyPI, so a stale local uv resolves and locks against a trust store that still includes the compromised eMudhra chains. Lock hashes protect installs, but not the lock step itself.
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The narrowly scoped configuration change matches existing pins and has no unresolved findings.
No open issues 🎉
What changed in this PR
Sets a minimum uv version for local development, aligning with the existing Docker and documentation workflow pins.
Changes:
- Requires uv ≥ 0.13.4 and documents the bundled CA trust-store rationale.
| File | Description |
|---|---|
pyproject.toml |
Adds the uv version floor and explanatory comments. |
Review effort: Balanced
janriokrause
approved these changes
Oct 21, 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.
One-line summary
Add a
required-versionfloor for uv matching the Dockerfile pin.Significant changes and points to review
One line under
[tool.uv]. uv carries its own CA roots for PyPI traffic, so a developerrunning an older uv locally would resolve and lock against a trust store that still includes
the compromised eMudhra chains.
--lockedinstalls are protected by the lock hashes, but thelock step that records those hashes is not. With the floor, an old uv refuses to run with a
clear message instead.
The Dockerfile and docs workflows already pin 0.13.4, so CI is unaffected. Developers below
0.13.4 need a one-time upgrade.
uv self updateworks for a standalone install. If uv livesinside a pyenv virtualenv, run the upgrade from outside the repo so the floor check does not
block it:
Issue / Bugzilla link
Follow-up to the eMudhra CA bump PR in this repo.
Testing
uv lock --checkpasses with uv 0.13.4 and is refused by 0.13.1 with the expected message.