Skip to content

chore(deps): update mem0ai requirement from >=0.1.0 to >=2.0.0#8

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/pip/mem0ai-gte-2.0.0
Closed

chore(deps): update mem0ai requirement from >=0.1.0 to >=2.0.0#8
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/pip/mem0ai-gte-2.0.0

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github Apr 18, 2026

Updates the requirements on mem0ai to permit the latest version.

Release notes

Sourced from mem0ai's releases.

Mem0 Python SDK (v2.0.0)

A ground-up redesign of how memories are extracted, stored, and retrieved — plus a long-overdue cleanup of the SDK surface.

Highlights

  • New extraction algorithm — single-pass, ADD-only, roughly half the latency
  • Multi-signal hybrid retrieval — semantic + BM25 keyword + entity matching fused into one score
  • Built-in entity linking — replaces graph memory with no external store to manage
  • Cleaner SDK surface — constructor and method signatures aligned with the Platform API

What's new

Single-pass ADD-only extraction

One LLM call per add(). No separate UPDATE/DELETE pass. The model now spends its capacity on understanding the input instead of diffing against existing memories, and agent-generated facts ("I've booked your flight for March 3rd") are captured as first-class memories for the first time. Hash-based deduplication prevents exact duplicates; ranking at retrieval time handles the rest.

Hybrid retrieval

Semantic vector similarity, BM25 keyword matching, and entity-graph boosting are normalized and fused into a single score on every result. The fusion adapts at runtime — if spaCy or fastembed aren't installed, search gracefully degrades to semantic-only instead of breaking.

Entity linking (replaces graph memory)

Entities (proper nouns, quoted text, compound noun phrases) are extracted automatically during add() and stored in a parallel {collection}_entities collection inside your existing vector store. At query time, entities from the query boost ranking on matching memories. No Neo4j, Memgraph, Kuzu, or Apache AGE deployment needed — ~4,000 lines of graph driver code have been removed from the SDK.

Vector store enhancements

All 15 vector stores now implement keyword_search() and search_batch(). Qdrant uses sparse vectors (BM25) alongside dense vectors in the same collection via fastembed; every other store uses its native full-text capability with no extra dependency.

Stricter, clearer validation

  • Empty or whitespace-only entity IDs raise ValueError with a specific message
  • threshold must be in [0, 1] — out-of-range values raise instead of silently behaving oddly
  • messages=None or wrong type raises Mem0ValidationError (code VALIDATION_003)
  • custom_fact_extraction_prompt → renamed to custom_instructions (consolidates with custom_update_memory_prompt, which was deprecated)

Platform client

  • MemoryClient(api_key="...")org_id / project_id no longer in the constructor
  • get_all returns a paginated envelope: {count, next, previous, results}
  • add is async by default and returns {status: "PENDING", event_id} — poll /v1/event/{event_id}/ for completion
  • Removed: api_version, output_format, async_mode, enable_graph, filter_memories, expiration_date, keyword_search, force_add_only, batch_size, immutable, includes, excludes, org_name, project_name

Breaking changes at a glance

Change Migration
Entity IDs on search() / get_all() Must be inside filters={"user_id": "..."}; top-level kwargs now raise ValueError
top_k default 10020 Pass top_k=100 explicitly to restore
threshold default None0.1 Pass threshold=0.0 to disable
rerank default TrueFalse Pass rerank=True to restore
graph_store / enable_graph Removed — uninstall graph drivers
custom_update_memory_prompt Removed — use custom_instructions
qdrant-client Bumped to >=1.12.0
upstash-vector Bumped to >=0.6.0

... (truncated)

Commits
  • fb22408 chore(release): promote Python SDK to 2.0.0 and TS SDK to 3.0.0 (#4860)
  • 30469ae docs: new algorithm migration guides + memory evaluation (#4811)
  • 50db9e4 chore(release): bump SDK versions to next beta (#4859)
  • fb87349 fix(oss): v3 entity cleanup, filter fixes, and QA hardening (TS + Python) (#4...
  • 8827553 fix: adopt new v3 memory endpoints in Python + TS clients (#4856)
  • c8e20a9 fix(docs): resolve duplicate operationIds and expiration_date type in openapi...
  • 93a51f4 test: update integration tests for v1.1 output_format (#4847)
  • 86fe275 fix(ts): entity store isolation, backward compat, pgvector + redis init fixes...
  • e6d6276 refactor: add entity ID and search param validation, rename textLemmatized fi...
  • 9692726 fix(ts-oss): isolate entity store from memory store by default (#4829)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Apr 18, 2026
Updates the requirements on [mem0ai](https://github.com/mem0ai/mem0) to permit the latest version.
- [Release notes](https://github.com/mem0ai/mem0/releases)
- [Commits](mem0ai/mem0@v0.1.0...v2.0.0)

---
updated-dependencies:
- dependency-name: mem0ai
  dependency-version: 2.0.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/pip/mem0ai-gte-2.0.0 branch from ff73feb to 6629089 Compare April 19, 2026 18:33
@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github May 2, 2026

Superseded by #9.

@dependabot dependabot Bot closed this May 2, 2026
@dependabot dependabot Bot deleted the dependabot/pip/mem0ai-gte-2.0.0 branch May 2, 2026 13:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants