Fix false update-available reports in git checks
Cluster 84851 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #86331 on 14 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 #86331. 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 items address incorrect update status reporting when a local checkout is ahead of or equal to upstream, specifically in the SSH fast path and local git check logic. The fixes aim to count behind-commits accurately rather than producing misleading 'update available' or 'commits behind' results.
Open issues0
Open PRs0
Fixes on record
-
#86331 fix(update-check): local-ahead checkouts read up to date, not 'update available'
files:
apps/desktop/electron/main.ts,hermes_cli/banner.py,tests/hermes_cli/test_banner_git_state.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#84860 fix(update): count real behind commits in SSH fast path · merged via another change →
3f39f80,#86331
Closed issues · 1
- Closed#84851SSH fast path in _check_via_local_git reports false "1 commit behind" when HEAD is ahead of upstream (carried commit)
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
- #86331
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 14 Aug 2026