Cairn
NousResearch/hermes-agent

Nix npmDepsHash staleness fixes and automation

Cluster 15314 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #16285. That is separate from the fix event.
Still open
Nothing open on GitHub.

Multiple bug reports and fixes addressing recurring stale npmDepsHash values in the Nix flake for hermes-tui, plus an effort to automate hash updates on push to main to prevent repeated CI breakage.

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.

  • #16285 ci(nix): auto-fix stale npm hashes on push to main

    merged to main

    files: .github/workflows/nix-lockfile-check.yml, .github/workflows/nix-lockfile-fix.yml, nix/lib.nix

3 PRs closed without merging

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

  • #15420 fix(nix): refresh tui + web npmDepsHash to unblock CI on every PR (#15244, #15272, #15314) · superseded by another PR → #15444
  • #19766 fix(nix): update npmDepsHash for hermes-tui · duplicate → #19764
  • #63771 feat(mcp): add playwright preset to hermes mcp add · superseded by another PR → #68488, #19760
Closed issues · 2
  • Closed#15314[Bug]: hermes-tui npmDepsHash is out of date (same root cause as #15272/#15244)
  • Closed#19760[Bug]: Build failure in Nix flake: `npmDepsHash` is out of date for `hermes-tui`
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.29: 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
#16285
Closed issues
2
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/15314.json
cluster/15314.md