Mem0 Node SDK (v3.3.1)
Mem0 releases published Mem0 Node SDK (v3.3.1). Bug Fixes: - Config (OSS): ConfigManager no longer injects OpenAI's default baseURL and model into non-OpenAI LLM providers. The defaults now apply only to openai and openai structured , so a DeepSeek, xAI, or other provider config without an explicit baseURL or model falls back to that provider's own defaults…
Why this signal matters
Mem0 releases published Mem0 Node SDK (v3.3.1). This release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: Bug Fixes: - Config (OSS): ConfigManager no longer injects OpenAI's default baseURL and model into non-OpenAI LLM providers. The defaults now apply only to openai and openai structured , so a DeepSeek, xAI, or other provider config without an explicit baseURL or model falls back to that provider's own defaults and env vars ( DEEPSEEK API BASE , XAI API BASE , ...) instead of pointing at OpenAI with an OpenAI model name ( 7350 (https://github.com/mem0ai/mem0/pull/7350)) - Vector Stores: Turbopuffer filters now apply every operator ( eq , ne , gt , gte , lt , lte , in , nin ). Only the range operators were read before, so eq , ne , in , and nin were silently dropped. A " " value now matches anything instead of nothing, an array value is treated as in , and an unsupported operator throws ( 6578 (https://github.com/mem0ai/mem0/pull/6578)) - Vector Stores: Turbopuffer search() with euclidean…
Actionable summary
Treat Mem0 Node SDK (v3.3.1) as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.
- Agent usefulness
- 82/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Review the official Mem0 releases release notes before upgrading.
- Check compatibility, migration, and security notes against your current agent stack.
- Run focused regression tests before production rollout.