Skip to content

Override Home Assistant's uv pin with >=0.13.4 - #95

Merged
jeyrb merged 1 commit into
mainfrom
security/uv-override
Oct 21, 2026
Merged

jeyrb merged 1 commit into
mainfrom
security/uv-override

Conversation

@jeyrb

@jeyrb jeyrb commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

homeassistant pins uv exactly: 0.12.23 in 2026.10.x, and still only 0.13.0 on HA's dev branch. That lands .venv/bin/uv at 0.12.23. Under uv run the venv's bin comes first on PATH, so anything run inside the project that calls uv gets the old version, not the mise-managed one. 0.12.23 is affected by GHSA-hq85-5cpj-mr62 (critical: emSign root, part of the eMudhra CA compromise) and GHSA-2cv4-cqwr-gwf7.

  • Adds uv>=0.13.4 to override-dependencies. This affects only the dev/CI lock; Home Assistant installs its own uv at runtime. The lock only changes uv.
  • Exempts uv from the exclude-newer cooldown, as the other HA repos already do. uv 0.13.4 came out on 2026-10-20.

Tested locally: uv run uv --version now gives 0.13.4 (it was 0.12.23); pytest 262 passed; ruff clean.

Context: security report 2026-10-20, addendum.

🤖 Generated with Claude Code

- homeassistant pins uv exactly (0.12.23 in 2026.10.x, 0.13.0 on dev);
  under `uv run` the venv's uv is first on PATH, so it shadows the
  mise-managed uv and anything run in the project uses the old version
- 0.12.23 is affected by GHSA-hq85-5cpj-mr62 (emSign root, eMudhra CA
  compromise) and GHSA-2cv4-cqwr-gwf7
- dev/CI lock only; Home Assistant installs its own uv at runtime

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jeyrb
jeyrb merged commit 832ecd5 into main Oct 21, 2026
12 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant