Fleet update reliability and deployment coordination
Cluster 91277 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #96311 on 27 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 #96311. 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 relate to improving the reliability and consistency of fleet update mechanisms, including deployment planning across install types, stdout/sentinel handling for desktop handshakes, and UX work for canary rollouts.
Open issues0
Open PRs0
Fixes on record
-
#96311 fix(serve): write machine sentinels to real fd 1 so the desktop handshake survives the stdout redirect (#96282)
files:
contributors/emails/[redacted:email],hermes_cli/web_server.py,tests/hermes_cli/test_serve_port_in_use.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#93042 feat(update): complete Phase 4 fleet UX and canary rollouts (#91277) · done elsewhere →
48c11b0,#96282,#96311,#96280,#96315
Closed issues · 1
- Closed#91277[Tracking] Fleet update reliability: one deployment plan for local, multi-profile, remote, and image-managed installs
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
- #96311
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 27 Aug 2026