NousResearch/hermes-agent
Automated upgrade path for self-managed Node.js runtime
Cluster 106456 · apps/bootstrap-installer. Data as of
1 open item. Fix attempted, not merged.
The short answer
0open issues
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue 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
- 0 issues and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab task
These items concern adding a safe, documented, or automated mechanism to upgrade the Hermes-managed Node.js runtime, including a proposed hermes doctor --upgrade-node command and a public upgrade_managed_node function in the node-bootstrap layer.
Open issues0
Open PRs1
- PR#106498feat(node-bootstrap): public upgrade_managed_node for the self-managed Node runtime
1 PR closed without merging
From the close comments: other 1
-
#106782 feat(node): safe managed-Node upgrade via hermes doctor --upgrade-node · other →
#122443
Closed issues · 1
- Closed#106456[Feature]: Provide a documented or automated mechanism to upgrade the self-managed Node.js runtime (~/.hermes/node)
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.00means 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 LabAt a glance
- Subsystem
- apps/bootstrap-installer
- Closed issues
- 1
- Attempts
- 1 PR closed without merging