NousResearch/hermes-agent

Fleet check errors for non-gateway runtime updates

Cluster 97332. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #103478 on 5 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #103478. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #103478. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #103478, then check it covers your case.

Read #103478 Pick up a Lab task

These issues and fixes address a bug where updating dashboard-only or unmapped runtimes incorrectly triggers gateway fleet verification, causing successful updates to exit with an error. The fix scopes fleet-probe checks to gateway-kind plan records only.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#103478 fix(update): fleet check no longer fails with "no rows" after stopping unmapped/dashboard-only runtimes; receipts survive the module purge (#97332, #98436, salvage #97350 #92934)

merged to main

files: contributors/emails/[redacted:email], hermes_cli/update_cmd_fleet.py, hermes_cli/update_cmd_maint.py, tests/hermes_cli/test_update_fleet_check_fail_closed.py, tests/hermes_cli/test_update_fleet_probe_resume_token.py, tests/hermes_cli/test_update_stale_module_purge.py

2 PRs closed without merging

From the close comments: merged via another change 2

#97350 fix(update): scope fleet-probe runtime expectation to gateway-kind plan records · merged via another change → f58fcc8, #103478, #97332
#97450 fix(update): only require fleet verification for gateway runtimes · merged via another change → f58fcc8, #103478, #97350

Closed issues · 1

Closed#97332[Bug]: dashboard-only runtime makes successful `hermes update` exit 1 on empty gateway fleet check

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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Merged PRs: #103478
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 5 Sep 2026

For your agent

The same facts, typed.

cluster/97332.json
cluster/97332.md