Fix false-positive rollback on docs-only stash restore
Cluster 130101 · hermes cli. Data as of
1 open item. Fix merged in #133056 on 7 Oct 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 #133056. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #133056. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
A bug caused the update process to incorrectly treat a successful relaunch probe (SystemExit) as an import failure during stash restore, triggering unnecessary rollback and exit 1. The fixes ensure docs-only local edits and successful probes no longer cause false-positive health check failures.
Open issues0
Open PRs1
- PR#130102fix(update): ignore successful relaunch probes during stash restore
Fixes on record
-
#133056 fix(update): a docs-only local edit no longer makes hermes update roll back and exit 1 (#130101)
files:
hermes_cli/update_cmd_stash.py,tests/hermes_cli/test_update_autostash.py
Closed issues · 1
- Closed#130101[Bug]: stash-restore health check false-positives on a docs-only stash (probe reports SystemExit as an import failure) — update rolls back, skips the gateway restart, exits 1
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
- #133056
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 7 Oct 2026