NousResearch/hermes-agent

Shallow fetch ancestry mis-detection causing wrong force-reset

Cluster 123346. Data as of

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

The short answer

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

These issues and fixes concern a bug where the update command incorrectly detects orphan divergence on shallow, partial, or stale clones and force-resets the branch. The work involves repairing ancestry checks after deepening a shallow fetch before any reset is performed.

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.

  • #126150 hermes update works on shallow, stale and partial-clone checkouts (salvage #122430, #123312, #124293, #124671)

    merged to main

    files: hermes_cli/gitlock.py, hermes_cli/update_cmd.py, hermes_cli/update_cmd_check.py, tests/e2e/core/upgrade/git/test_partial_clone.py, tests/e2e/core/upgrade/git/test_shallow_install.py, tests/hermes_cli/test_gitlock.py, tests/hermes_cli/test_shallow_boundary_repair.py, tests/hermes_cli/test_shallow_graft_prune.py, tests/hermes_cli/test_tag_fetch_partial_clone.py, tests/hermes_cli/test_update_shallow_heal.py

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #123476 fix(cli): re-test ancestry after deepening a shallow fetch before resetting · superseded by another PR → #126150
  • #123727 fix(update): repair shallow-poisoned ancestry before force-resetting the branch (fixes #123346) · superseded by another PR → #126150, #123346
Closed issues · 1
  • Closed#123346hermes update mis-detects orphan divergence after a --depth pre-fetch and force-resets the branch
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
#126150
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
28 Sep 2026

For your agent

The same facts, typed.