Nothing open on GitHub. Fix merged in #124684 on 27 Sep 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 #124684. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #124684. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where a single transient HTTP error (503/429) during a release-channel read aborts a Hermes update with no retry, ignoring Retry-After headers. The cluster covers the problem report, a salvage/workaround, and a fix adding retry behavior.
Open issues0
Open PRs0
Fixes on record
-
#124684 hermes update rides out a CDN blip on the release-channel read; passive checks stay single-shot (salvage #124663)
files:
hermes_cli/release_channels.py,hermes_cli/update_cmd.py,tests/e2e/core/upgrade/network/test_offline_and_flaky.py,tests/hermes_cli/test_release_channels.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#124663 fix(update): retry transient release channel reads · merged via another change →
d25bbd0,#124684
Closed issues · 1
- Closed#124653hermes update: one transient 503/429 on the release-channel record aborts the update (no retry, Retry-After ignored)
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
- Merged PRs
- #124684
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 27 Sep 2026