Nothing open on GitHub. Fix merged in #100643 on 1 Sep 2026. Check it covers your case.
The short answer
0open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #100643. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #100643. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests concern a gap where pre- and post-update state.db emergency backup logic applied only to the root database, leaving per-profile databases unprotected. The work addresses extending that guard to cover every profile.
Open issues0
Open PRs0
Fixes on record
-
#100643 fix(update): post-update state.db guard covers every profile (salvage #99954)
files:
hermes_cli/update_cmd.py,tests/hermes_cli/test_update_state_autorestore.py
2 PRs closed without merging
From the close comments: merged via another change 1 · stale or abandoned 1
Closed issues · 1
- Closed#97994[Bug]: pre-update state.db guard (#68474) covers only the root DB — profile databases get no emergency backup
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
- #100643
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 1 Sep 2026