Stale git shallow lock blocks update fetch
Cluster 75133 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #86928 on 15 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 #86928. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a stale .git/shallow.lock file that blocks update fetches, including a reported symptom of being stuck on 'Hermes is still running' and proposed fixes to remove or self-heal the lock before fetching.
Open issues0
Open PRs0
Fixes on record
-
#86928 fix(update): self-heal stale git locks that wedge every update fetch
files:
apps/desktop/electron/gitlock.test.ts,apps/desktop/electron/gitlock.ts,apps/desktop/electron/main.ts,contributors/emails/[redacted:email],hermes_cli/banner.py,hermes_cli/gitlock.py,hermes_cli/update_cmd.py,tests/test_gitlock.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#75168 fix(update): remove stale .git/shallow.lock before fetch (#75133) · done elsewhere →
#75133,#86928,#80501
Closed issues · 1
- Closed#75133[Bug]: Stuck on "Hermes is still running" caused by stale .git/shallow.lock after interrupted update
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
- #86928
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Aug 2026