diff --git a/pyproject.toml b/pyproject.toml index 9f00675d..62056664 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -33,7 +33,7 @@ dependencies = [ # sustained churn (bounded + reclaimable index dir, no compaction crash) — see # docs/cascade_runbook.md. Never widen this floor back below 0.34 (older lance # cannot read v8 data). - "lancedb>=0.34.0,<0.35.0", # Vector + BM25 + scalar filter (Arrow-based) + "lancedb>=0.34.0,<0.41.0", # Vector + BM25 + scalar filter (Arrow-based) # Floor, not a new package: lancedb pulls pyarrow in anyway. 25.0.1 stops # the per-value `import pytz` attempt in to_pylist() (24 walked sys.path # for every tz-aware timestamp) and materialises rows without a Scalar @@ -47,7 +47,7 @@ dependencies = [ # LLM & embedding (one provider per file pattern) # <3: openai 3.x (2026-09-24) moved to the httpx 1.0 pre-release line and its # client raises AttributeError on every request; 2.x is what the lock tests. - "openai>=1.0.0,<3", + "openai>=1.0.0,<4", # Markdown / file system "PyYAML>=6.0", # YAML frontmatter parsing @@ -88,10 +88,10 @@ dependencies = [ "anyio>=4.0", # Async file I/O (anyio.Path, to_thread.run_sync) for the markdown layer # Algorithm library (everalgo monorepo, published on PyPI). - "everalgo-user-memory==0.4.0", - "everalgo-agent-memory==0.4.0", + "everalgo-user-memory==0.7.0", + "everalgo-agent-memory==0.5.1", "everalgo-rank==0.4.1", - "everalgo-knowledge==0.1.1", + "everalgo-knowledge==0.2.1", # everalgo's own transitive layer, pinned to what this repo's uv.lock — # and therefore the whole test suite — actually resolves. The packages @@ -104,8 +104,8 @@ dependencies = [ # (`memorize.mode = "agent"`) install of 1.2.3 while every local suite # stayed green on the locked 0.2.1. Raise these deliberately, together # with a run of the release smoke against a PyPI-resolved install. - "everalgo-boundary==0.2.1", - "everalgo-core==0.3.0", + "everalgo-boundary==0.3.0", + "everalgo-core==0.5.1", "everalgo-clustering==0.2.1", ]