fix(livekit): cap supermemory below 5

supermemory>=3.50.0 has no upper bound, so a fresh install resolves to
5.0.1. The plugin still makes 3.x SDK calls, which fail on 5.x, and its
fail-open error handling turns those failures into log warnings, so the
agent runs with no memory. Cap below 5, as #1774 did for the other Python
wrappers. The cap lifts when the package moves to v5.

Fixes #1860

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Abhishek Sharma 2026-11-02 07:47:44 +05:30
parent 8b47bd17c2
commit abd9252cdc
2 changed files with 5 additions and 5 deletions

View file

@ -171,10 +171,10 @@ A Bun + Turbo monorepo. The `supermemory` SDKs on npm and PyPI are built in sepa
- Bump versions in `packages/tools/package.json`, `packages/memory-graph/package.json` or
`packages/*-python/pyproject.toml` unless asked. The `publish-*.yml` workflows publish when those change on `main`.
- Edit the workflows in `.github/workflows/` unless asked.
- Migrate the Python packages to the v5 SDK unless asked. `openai-sdk-python`, `pipecat-sdk-python` and
`cartesia-sdk-python` pin `supermemory<5` (the 3.x SDK) on purpose, and `livekit-sdk-python` still makes uncapped 3.x
SDK calls; all of them use `container_tag`. `agent-framework-python` 2.0 is already on v5 (`supermemory>=5.0.0,<6`)
and passes its `container_tag` as the namespace.
- Migrate the Python packages to the v5 SDK unless asked. `openai-sdk-python`, `pipecat-sdk-python`,
`cartesia-sdk-python` and `livekit-sdk-python` pin `supermemory<5` (the 3.x SDK) on purpose; all of them use
`container_tag`. `agent-framework-python` 2.0 is already on v5 (`supermemory>=5.0.0,<6`) and passes its
`container_tag` as the namespace.
- Commit `.env` files, API keys or credentials.
### Repository map

View file

@ -32,7 +32,7 @@ classifiers = [
dependencies = [
"livekit-agents>=1.3.6,<2",
"pydantic>=2.10.0",
"supermemory>=3.50.0",
"supermemory>=3.50.0,<5",
]
[project.optional-dependencies]