NousResearch/hermes-agent

hermes update stable channel ancestry probe timeout handling

Cluster 137646 · hermes cli. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #139079 on 15 Oct 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #139079 Pick up a Lab task

These members concern hermes update on the stable channel, where a 10-second git ancestry probe for an unfetched release commit is reported to time out and lead to the update being refused. One member is a bug report and the other two are changes (one referencing a salvage of #137646) that address how an unanswered probe is handled.

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.

#139079 hermes update no longer refuses the stable channel when git is slow to find the unfetched release (#137646, salvage #137649)

merged to main

files: contributors/emails/[redacted:email], hermes_cli/source_releases.py, tests/hermes_cli/test_gateway_chat_native.py, tests/hermes_cli/test_stable_forward_only_shallow.py

1 PR closed without merging

From the close comments: merged via another change 1

#137649 fix(update): an ancestry probe git never answered does not refuse the update · merged via another change → 3bdb82d, #139079, #137646

Closed issues · 1

Closed#137646[Bug]: `hermes update` refuses the stable channel when the release commit is not local (10 s ancestry probe times out)

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.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

Subsystem: hermes cli
Merged PRs: #139079
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 15 Oct 2026

For your agent

The same facts, typed.

cluster/137646.json
cluster/137646.md