CLI update-check caching stale or incorrect results
Cluster 82166 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #95492 on 26 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 #95492. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #95492. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where a failed or incomplete git fetch causes the CLI's update-check mechanism to cache and serve incorrect 'up to date' results, potentially hiding available releases for an extended period.
Open issues0
Open PRs0
Fixes on record
-
#95492 fix(cli): a failed git fetch can no longer cache a false 'up to date' for 6 hours (#82166, salvage #83367)
files:
hermes_cli/banner.py,tests/hermes_cli/test_update_check.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#83367 fix(cli): don't serve stale update-check results after fetch failure · merged via another change →
98e87ac,#95492,#92578,#82166
Closed issues · 1
- Closed#82166Update-check endpoint reports "up to date" for multiple consecutive days while a real release is available (inverse of the known stale-cache issue in #11007 / #1620)
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
- #95492
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 26 Aug 2026