Repository navigation
fix(deps): bump mem0ai exact pins from 2.0.10 to 2.0.19 - #98416
Closed
salch-cred wants to merge 1 commit into
Closed
salch-cred wants to merge 1 commit into
salch-cred wants to merge 1 commit into
Conversation
The project-extra and lazy-install paths both pinned mem0ai==2.0.10 (June 2026), while the plugin manifest already accepted >=2.0.10,<3. mem0ai 2.0.19 is the current stable release. Changes: - pyproject.toml [project.optional-dependencies] mem0 extra: 2.0.10 -> 2.0.19 - tools/lazy_deps.py memory.mem0 lazy feature: 2.0.10 -> 2.0.19 - uv.lock: regenerated with 'uv lock --upgrade-package mem0ai' - [tool.uv] exclude-newer-package: add mem0ai = false so the 14-day cutoff does not brick installs of the newly-reviewed pin Upstream compatibility: Python support, base runtime deps, and the Memory.update(data=...) spelling Hermes uses are all unchanged between 2.0.10 and 2.0.19. No lock movement outside mem0ai itself. The plugin manifest (mem0ai>=2.0.10,<3) is not changed. Fixes NousResearch#98407
alt-glitch
added
type/bug
|
Independent verification for this exact diff:
I opened #98420 after a pre-create race missed this PR. I am closing that later duplicate in favor of this one. |
11 of 19 tasks
teknium1
added a commit
that referenced
this pull request
Sep 22, 2026
…mes list-typed files and reads hooks: - hindsight-client==0.6.1 / mem0ai==2.0.10 exact pins made _is_satisfied() reject every newer compatible release, so hermes update kept downgrading a working client and broke embedded daemons whose DB a newer client had migrated (#86992, #39424, #98407, #99317). The lazy entries now mirror the plugin manifests (>=0.6.1,<1 and >=2.0.10,<3); pyproject extras stay the floor install. Slim redo of #99557 (nateEc) / #98416 / #98527 (ttomiczek) / #39754. - A list-typed plugin.yaml is refused with "top level must be a mapping" instead of an AttributeError swallowed as "Failed to parse" (#14066, discovery side). - ``hooks:`` (the spelling bundled manifests carried) still populates provides_hooks (#108371).
teknium1
added a commit
that referenced
this pull request
Sep 22, 2026
…mes list-typed files and reads hooks: - hindsight-client==0.6.1 / mem0ai==2.0.10 exact pins made _is_satisfied() reject every newer compatible release, so hermes update kept downgrading a working client and broke embedded daemons whose DB a newer client had migrated (#86992, #39424, #98407, #99317). The lazy entries now mirror the plugin manifests (>=0.6.1,<1 and >=2.0.10,<3); pyproject extras stay the floor install. Slim redo of #99557 (nateEc) / #98416 / #98527 (ttomiczek) / #39754. - A list-typed plugin.yaml is refused with "top level must be a mapping" instead of an AttributeError swallowed as "Failed to parse" (#14066, discovery side). - ``hooks:`` (the spelling bundled manifests carried) still populates provides_hooks (#108371).
This was referenced Sep 22, 2026
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Both
mem0aiinstall paths in the repository were pinned to2.0.10(June 2026) while the current stable release is2.0.19. The plugin manifest already accepted>=2.0.10,<3, but eager installs (project extra) and lazy installs (tools/lazy_deps.py) both resolved the stale pin.Changes
pyproject.tomlmem0 = ["mem0ai==2.0.10"]→mem0ai==2.0.19tools/lazy_deps.py"memory.mem0": ("mem0ai==2.0.10",)→mem0ai==2.0.19uv.lockuv lock --upgrade-package mem0ai— onlymem0aimovespyproject.toml[tool.uv]mem0ai = falsetoexclude-newer-packageso the 14-day cutoff does not brick installs of the newly-reviewed pinCompatibility evidence
>=3.10,<4.0Memory.update(data=...)(the spelling Hermes uses at the adapter boundary) remains a supported aliasmem0aiitselfWhat was not changed
The plugin manifest (
plugins/memory/mem0/plugin.yaml:mem0ai>=2.0.10,<3) retains its broader compatibility range — no evidence requires raising the minimum above 2.0.10 for supported setups.Fixes #98407.