Cairn
NousResearch/hermes-agent

Node.js deps skipped on already-current checkout fix

Cluster 77211. Data as of

Nothing open on GitHub. Fix merged in #85539. Check it covers your case.

The short answer

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

These items address a bug where running an update on an already-current checkout skips the Node.js dependency refresh, leaving a previously broken install unrepaired. The work adds a health check so dependencies are re-synced even when no new checkout is needed.

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.

  • #85539 fix(update): 'Already up to date' no longer skips repairing a failed Node dependency install

    merged to main

    files: hermes_cli/update_cmd.py, tests/hermes_cli/test_update_current_node_repair.py

3 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1 · superseded by another PR 1

  • #77231 fix(update): check Node.js deps health on already-current checkout (#77211) · done elsewhere → #85539
  • #77350 fix(cli): 已在当前分支路径中增加 Node.js 依赖和 Web UI 自愈检查 · duplicate → #77231
  • #77546 fix(update): re-sync Node.js deps on already-current checkout (#77211) · superseded by another PR → #85539
Closed issues · 1
  • Closed#77211`hermes update` on an already-current checkout skips the Node.js dependency refresh — a previously failed npm install is never repaired, despite the error telling the user to "re-run hermes update"
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.40: 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
#85539
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
13 Aug 2026

For your agent

The same facts, typed.

cluster/77211.json
cluster/77211.md