venv repair preserving memory-provider packages
Cluster 113741. Data as of
Nothing open on GitHub. Fix merged in #114805 on 19 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #114805. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #114805. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where the virtual environment repair process fails to maintain or reinstall the active memory provider's dependencies. The fixes target the specific repair code paths to ensure memory-provider bridge packages are kept intact.
Open issues0
Open PRs0
Fixes on record
-
#114805 fix(update): venv repair keeps the active memory provider's packages installed (#113741, salvage #113747)
files:
hermes_cli/update_cmd.py,tests/hermes_cli/test_cmd_update.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#113747 fix(cli): heal memory-provider bridge packages on every venv repair path · merged via another change →
6c16233,#114805,#113741,#113747
Closed issues · 1
- Closed#113741venv repair path skips memory-provider dependency refresh
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
- Merged PRs
- #114805
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Sep 2026