Windows installer mishandles uv shims from package managers
NousResearch/hermes-agent · cluster 110350
Data as of
Nothing open on GitHub. Fix merged in #115679. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #115679. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #115679. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where the Windows installer incorrectly accepts or copies uv shims from package managers like Chocolatey, and propose fixes to detect and reject such shims while also self-healing the managed uv installation on rerun.
Open issues0
Open PRs0
Fixes on record
-
#115679 fix(install): Windows installer rejects relocated uv shims and self-heals the managed uv (#110350, salvage #110355)
files:
.github/workflows/installer-tests.yml,hermes_cli/managed_uv.py,scripts/install.ps1,scripts/tests/test-install-ps1-uv-shim-validation.ps1,tests/hermes_cli/test_managed_uv.py
5 PRs closed without merging
From the close comments: done elsewhere 2 · duplicate 2 · merged via another change 1
-
#110355 fix(install): reject broken copied uv shims · merged via another change →
4d59f89,#115679 -
#110375 fix(installer): reject unusable Chocolatey uv shims · duplicate →
#110355,#110378 -
#110378 fix(installer): resolve package manager shim targets and self-heal managed uv on rerun · duplicate →
#110355,#110350 -
#110421 fix(installer): resolve package manager shim targets and self-heal managed uv on rerun · done elsewhere →
4d59f89,#115679 -
#114634 fix(install.ps1): reject broken/relocated package-manager uv shims; self-heal managed uv (#110350) · done elsewhere →
4d59f89,#115679
Closed issues · 1
- Closed#110350[Bug]: Windows installer copies Chocolatey uv shim and fails Python 3.11 verification
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.29: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #115679
- Closed issues
- 1
- Attempts
- 5 PRs closed without merging
- Fix link checked
- 19 Sep 2026