WSL update picking Windows npm, misreporting dependency refresh errors
Cluster 30271 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #65528 on 16 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #65528. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #65528. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The members concern the CLI update path on WSL, where Windows npm may be looked up instead of a Linux-native one, and where an error during the Node dependency refresh may still be reported as a complete update. Three titles describe fixes (one a salvage of an earlier change) and one is a bug report; their outcomes are not stated here.
Open issues0
Open PRs0
Fixes on record
-
#65528 fix(cli): don't run Windows npm on WSL update + honest partial-failure reporting (#36034 salvage)
files:
hermes_cli/main.py,tests/hermes_cli/test_cmd_update.py
2 PRs closed without merging
From the close comments: merged via another change 1 · stale or abandoned 1
Closed issues · 1
- Closed#30271[Bug] WSL update path resolves Windows npm, breaks ui-tui dependency refresh, but still reports "Update complete!"
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.50: 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
- Subsystem
- hermes cli
- Merged PRs
- #65528
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 16 Jul 2026