Thanks for the context here. I swept through the related work, and this is now duplicate or superseded.

Close as duplicate/superseded: the same memory-lancedb dependency conflict is already tracked in #90295, and #90407 is the open fix path for aligning Arrow with LanceDB's peer range.

Canonical path: Track and land the dependency alignment through #90295 and #90407 rather than keeping this duplicate issue open.

So I’m closing this here and keeping the remaining discussion on #90295 and #90407.

Review details

Best possible solution:

Track and land the dependency alignment through #90295 and #90407 rather than keeping this duplicate issue open.

Do we have a high-confidence way to reproduce the issue?

Yes. Source and npm registry metadata show the package asks npm to install apache-arrow@21.1.0 while @lancedb/lancedb@0.30.0 peers only allow <=18.1.0; I did not run an install because this review is read-only.

Is this the best way to solve the issue?

Yes. The best path is to close this duplicate and continue review of the canonical issue and PR; the actual fix should align the plugin manifest, shrinkwrap, and lockfile with LanceDB's peer contract.

Security review:

Security review: No patch is under review; this is ordinary issue triage for a dependency-version conflict.

AGENTS.md: found and applied where relevant.

What I checked:

Canonical issue already owns the same bug: GitHub search and live issue data show memory-lancedb 2026.6.1 fails to install: apache-arrow 21.1.0 conflicts with @lancedb/lancedb 0.30.0 peer range #90295 is open and reports the same @openclaw/memory-lancedb@2026.6.1 install failure: apache-arrow@21.1.0 conflicts with @lancedb/lancedb@0.30.0 peer range.
Open fixing PR targets the canonical issue: fix(memory-lancedb): align apache arrow peer dependency #90407 is open and changes extensions/memory-lancedb/package.json, extensions/memory-lancedb/npm-shrinkwrap.json, and pnpm-lock.yaml to pin apache-arrow to 18.1.0, with PR text saying it fixes memory-lancedb 2026.6.1 fails to install: apache-arrow 21.1.0 conflicts with @lancedb/lancedb 0.30.0 peer range #90295.
Current main still has the reported dependency pair: Current main declares @lancedb/lancedb 0.30.0 and apache-arrow 21.1.0 in the memory-lancedb package manifest. (extensions/memory-lancedb/package.json:10, d4b4a658094e)
Checked-in shrinkwrap records the peer conflict: The memory-lancedb shrinkwrap root depends on apache-arrow 21.1.0, while the @lancedb/lancedb 0.30.0 entry declares peer dependency apache-arrow >=15.0.0 <=18.1.0. (extensions/memory-lancedb/npm-shrinkwrap.json:47, d4b4a658094e)
Registry metadata confirms the dependency contract: npm metadata for @lancedb/lancedb@0.30.0 declares peerDependencies.apache-arrow as >=15.0.0 <=18.1.0, and npm metadata for @openclaw/memory-lancedb@2026.6.1 declares both apache-arrow@21.1.0 and @lancedb/lancedb@0.30.0.
Latest release contains the same mismatch: The v2026.6.1 release tag has the same memory-lancedb dependency pair and shrinkwrap peer range, matching the reported published package behavior. (extensions/memory-lancedb/package.json:10, 2e08f0f4221f)

Likely related people:

steipete: Git history shows the dependency update in 48ccc50282ebf41175aefe821903380a98b596bb changed memory-lancedb to the incompatible LanceDB/Arrow pair, and later release/version updates also touched the same package files. (role: introduced dependency pair and recent package-manifest contributor; confidence: high; commits: 48ccc50282eb, 8e28c773feb7, 25149801189f; files: extensions/memory-lancedb/package.json, extensions/memory-lancedb/npm-shrinkwrap.json)
amittell: Recent history shows substantial merged work in the memory-lancedb runtime, making this a useful secondary routing signal for validating plugin behavior after the package fix. (role: recent memory-lancedb runtime contributor; confidence: medium; commits: 945faf8e6798; files: extensions/memory-lancedb/index.ts)

Codex review notes: model gpt-5.5, reasoning high; reviewed against d4b4a658094e.

Uh oh!

Uh oh!

Issue on memory-lancedb #90877

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions