Gateway separate-checkout handling in hermes update
Cluster 117449. Data as of
Nothing open on GitHub. Fix merged in #117588 on 20 Sep 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 #117588. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117588. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where gateways running from a separate checkout caused hermes update to exit with an error, due to foreign code_sha being misclassified as STALE and fleet_restart_pending never clearing. The cluster covers the bug report and related fix attempts exempting or ignoring foreign checkout fleet rows.
Open issues0
Open PRs0
Fixes on record
-
#117588 fix(update): gateways running a separate checkout no longer fail hermes update forever (#117449, salvage #117473)
files:
hermes_cli/update_cmd_fleet.py,hermes_cli/update_receipt.py,tests/hermes_cli/test_update_external_checkout.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#117449`hermes update` always exits 1 when a profile's gateway runs from a separate checkout — foreign code_sha classified STALE, fleet_restart_pending never discharges
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
- Merged PRs
- #117588
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 20 Sep 2026