hermes-serve systemd unit restart on update
Cluster 83438 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #87859 on 16 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #87859. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #87859. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug was reported and fixes were proposed to ensure hermes-serve systemd units are restarted during updates, rather than leaving stale code running until a manual restart.
Open issues0
Open PRs0
Fixes on record
-
#87859 fix(update): restart hermes-serve systemd units alongside gateways (#83438)
files:
hermes_cli/dashboard_procs.py,hermes_cli/main.py,hermes_cli/update_cmd.py,tests/hermes_cli/test_update_fleet_restart_timeout.py,tests/hermes_cli/test_update_stale_dashboard.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#83595 fix(update): restart hermes-serve systemd units alongside gateways · merged via another change →
#87859,#83438
Closed issues · 1
- Closed#83438[Bug]: hermes update does not restart hermes-serve (Desktop backend) — leaves stale code running until manual restart
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.67: 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
- #87859
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Aug 2026