Symlinked profile gateway misclassified during update/restart
Cluster 120240 · hermes cli. Data as of
1 open item. Fix merged in #127035 on 29 Sep 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 #127035. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #127035. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
A bug where a profile under ~/.hermes/profiles/ that is a symlink to a separate Hermes install causes its gateway to be incorrectly classified during update and restart reconciliation. The fixes adjust the updater to recognize and skip such gateways as external rather than unaccounted.
Open issues0
Open PRs1
- PR#120254fix(updater): skip external profile gateways in restart reconciliation
Fixes on record
-
#127035 fix(update): report a symlinked other-install profile gateway as external, not unaccounted
files:
hermes_cli/update_cmd_fleet.py,hermes_cli/update_inventory.py,tests/hermes_cli/test_update_external_profile_reconciliation.py
Closed issues · 1
- Closed#120240[Bug]: `hermes update` exits 1 on every run when a profile under `~/.hermes/profiles/` is a symlink to a separate Hermes install (its gateway is marked "never touched")
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
- #127035
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 29 Sep 2026