Desktop update handling for network-bound serve and external venv blockers
Cluster 63206 · apps/desktop. Data as of
Nothing open on GitHub. Fix merged in #95576 on 26 Aug 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 #95576. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #95576. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The members appear related around in-app or CLI updates for Hermes Desktop when a network-bound hermes serve backend or an external venv is involved. One issue reports a Windows case lacking actionable recovery, while the pull requests propose keeping serve backends on their recorded endpoints across updates and surfacing external venv update blockers; two share the same title, one noted as a salvage of another.
Open issues0
Open PRs0
Fixes on record
-
#73569 fix(desktop): surface external venv update blockers (salvage #63318)
files:
apps/desktop/electron/main.ts,apps/desktop/electron/venv-blocker-scan.test.ts,apps/desktop/electron/venv-blocker-scan.ts,hermes_cli/_scan_venv_blockers.py,tests/hermes_cli/test_scan_venv_blockers.py -
#95576 feat(update): network-bound serve backends survive hermes update on their recorded endpoints (#63206)
files:
hermes_cli/dashboard_procs.py,hermes_cli/main.py,hermes_cli/process_identity.py,hermes_cli/update_cmd.py,hermes_cli/update_inventory.py,hermes_cli/web_server.py,tests/hermes_cli/test_dashboard_lifecycle_flags.py,tests/hermes_cli/test_serve_runtime_inventory.py,website/docs/getting-started/updating.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#63318 fix(desktop): surface external venv update blockers · merged via another change →
03af12c,#73569
Closed issues · 1
- Closed#63206[Windows] Network-bound hermes serve used by remote Desktop blocks in-app update without actionable recovery
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 Lab