Cairn

npm lockfile churn breaking desktop build stamps

NousResearch/hermes-agent · cluster 105659 · hermes cli

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

Fixes and a related bug report focused on preventing npm lockfile churn from invalidating desktop build stamps and causing repeated update autostashes, especially on Windows.

Open issues1

  • Issue#105659hermes update leaves package-lock.json dirty on Windows: desktop build stamp never matches again (stale-build verification failure + endless update autostashes)

Open PRs2

  • PR#105673fix(update): stop npm lockfile churn from invalidating desktop builds
  • PR#111994fix(desktop): resolve the build stamp at the profile-normalized root

1 PR closed without merging

From the close comments: duplicate 1

  • #105676 fix(update): preserve lockfile across npm installs · duplicate → #105673, #105659
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

Subsystem
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/105659.json
cluster/105659.md