NousResearch/hermes-agent

Windows venv recreation reliability and rollback

Cluster 83149 · apps/bootstrap-installer. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #86686 on 15 Aug 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #86686, then check it covers your case.

Read #86686 Pick up a Lab task

These items address a bug where an unsuccessful venv rename-aside on Windows could leave an installation in a broken, unrecoverable state. The work makes the recreation process transactional and ensures a safe abort when the rename step does not complete.

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.

#86686 fix(installer): transactional Windows venv recreation with dependency-stage rollback (#83149)

merged to main

files: hermes_cli/_scan_venv_blockers.py, scripts/install.ps1, tests/hermes_cli/test_scan_venv_blockers.py, tests/test_install_ps1_venv_recreate_safety.py, tests/test_install_ps1_venv_rename_abort.py, tests/test_install_ps1_venv_transaction_boundary.py, tests/test_install_unmerged_index.py, website/docs/getting-started/updating.md

2 PRs closed without merging

From the close comments: merged via another change 2

#83191 fix(install): abort Windows venv recreate when rename-aside fails (#83149) · merged via another change → #86686, #83194
#83194 fix(installer): make Windows venv recreation transactional (#83149) · merged via another change → #86686, #83191

Closed issues · 1

Closed#83149Windows: failed venv recreate falls back to a destructive in-place delete, leaving the install gutted with no rollback (and the blocker probe cannot run afterwards)

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.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: apps/bootstrap-installer
Merged PRs: #86686
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 15 Aug 2026

For your agent

The same facts, typed.

cluster/83149.json
cluster/83149.md