Repository navigation
Description
Summary
After upgrading OpenClaw from 2026.5.28 to 2026.6.1, the @openclaw/memory-lancedb@2026.6.1 plugin update fails during dependency installation and OpenClaw disables the plugin.
This appears to be a package dependency mismatch in the 2026.6.1 memory-lancedb bundle, not LanceDB data corruption.
Environment
- OpenClaw before upgrade:
2026.5.28 - OpenClaw after upgrade:
2026.6.1 (2e08f0f) - macOS:
26.5arm64 - Node:
24.14.1 - npm:
11.11.0 - Install type: npm
- Plugin being updated:
clawhub:@openclaw/memory-lancedb
Failure
openclaw update / openclaw plugins update memory-lancedb fails with npm ERESOLVE:
Failed to update memory-lancedb: npm install failed: npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @openclaw/memory-lancedb@2026.6.1
npm error Found: apache-arrow@21.1.0
npm error node_modules/apache-arrow
npm error apache-arrow@"21.1.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer apache-arrow@">=15.0.0 <=18.1.0" from @lancedb/lancedb@0.30.0
npm error node_modules/@lancedb/lancedb
npm error @lancedb/lancedb@"0.30.0" from the root project
Observed Result
- Core OpenClaw upgrade succeeds.
memory-lancedbupdate fails.- OpenClaw disables
memory-lancedbin config. - Memory slot falls back to
memory-core. - Repeated config warning appears:
plugins.entries.memory-lancedb: plugin disabled (disabled in config) but config is present
The previous memory-lancedb@2026.5.28 extension remains physically installed and the LanceDB store is still readable.
Expected Result
@openclaw/memory-lancedb@2026.6.1 should install cleanly under npm 11, or its package dependencies should align with the peer dependency declared by @lancedb/lancedb@0.30.0.
Specifically, either:
- do not require
apache-arrow@21.1.0while using@lancedb/lancedb@0.30.0, or - update the LanceDB dependency to a version whose peer range accepts Arrow 21, if such a version exists, or
- pin Arrow inside the accepted peer range.
Local Data Check
The LanceDB data itself appears intact. A local coverage audit against the existing store passed after the failed update:
ok=true
lancedb_total=9065
lancedb_lcm_sync=9060
ledger_rows=9060
Workaround Used Locally
I am temporarily restoring the previous active memory posture by re-enabling the still-installed memory-lancedb@2026.5.28 plugin in config, rather than forcing npm with --force or --legacy-peer-deps.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
clawsweeper commentedon Jun 4, 2026
Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 21, 2026, 1:50 PM ET / 17:50 UTC.
Summary
Keep open: current main, the latest release, and the currently published memory-lancedb package still carry the Arrow/LanceDB peer mismatch, while the linked repair PR is open and conflicting rather than merged.
Reproducibility: yes. Source, shrinkwrap, root lockfile, release tag, and live npm registry metadata show Arrow 21.1.0 outside LanceDB 0.30.0's accepted peer range; I did not run an install in this read-only review.
Root-cause cluster
Relationship:
canonicalCanonical: #90295
Summary: This issue is the canonical same-repository report for the memory-lancedb Arrow/LanceDB peer mismatch; one duplicate is closed and one open PR is the fix candidate.
Members:
fixed_by_candidate: fix(memory-lancedb): align apache arrow peer dependency #90407 - The PR uses closing syntax for this issue and changes the memory-lancedb manifest, shrinkwrap, and root lockfile to align Arrow with LanceDB's peer range.duplicate: Issue on memory-lancedb #90877 - The closed issue reports the same memory-lancedb dependency incompatibility and its close comment points back to this issue plus the open fix PR.Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.
Next step
No new issue-derived fix PR should be queued because the open linked PR already owns the implementation path.
Review details
Best possible solution:
Land #90407 after trusted dependency-graph review, or apply the equivalent manifest, shrinkwrap, and lockfile repair from a maintainer branch and publish a fixed memory-lancedb package.
Do we have a high-confidence way to reproduce the issue?
Yes. Source, shrinkwrap, root lockfile, release tag, and live npm registry metadata show Arrow 21.1.0 outside LanceDB 0.30.0's accepted peer range; I did not run an install in this read-only review.
Is this the best way to solve the issue?
Yes. A narrow plugin-owned dependency graph alignment is the best fix; forcing npm peer resolution or adding runtime fallback would not repair the published package contract.
AGENTS.md: found and applied where relevant.
Remaining risk / open question:
Codex review notes: model internal, reasoning high; reviewed against eea777c9fc9c.
Label changes
Label justifications:
P2: This breaks install/update for one official memory plugin while core OpenClaw remains usable with the fallback memory path.impact:session-state: The failed update disables or displaces the configured LanceDB memory plugin, changing active memory and context behavior for affected users.Evidence reviewed
What I checked:
extensions/memory-lancedb/package.json:11, eea777c9fc9c)extensions/memory-lancedb/npm-shrinkwrap.json:11, eea777c9fc9c)pnpm-lock.yaml:1043, eea777c9fc9c)extensions/memory-lancedb/package.json:11, c645ec4555c0)Likely related people:
extensions/memory-lancedb/package.json,extensions/memory-lancedb/npm-shrinkwrap.json,pnpm-lock.yaml)extensions/memory-lancedb/package.json,extensions/memory-lancedb/npm-shrinkwrap.json,pnpm-lock.yaml)extensions/memory-lancedb/index.ts,extensions/memory-lancedb/index.test.ts)extensions/memory-lancedb/package.json,extensions/memory-lancedb/npm-shrinkwrap.json,pnpm-lock.yaml)How this review workflow works
@clawsweeper re-reviewcomments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.@clawsweeper re-reviewor@clawsweeper re-runon an open PR or issue to request a fresh review only.@clawsweeper reviewto request a fresh review only.@clawsweeper autofix,@clawsweeper automerge,@clawsweeper fix ci, or@clawsweeper address review.@clawsweeper explainto ask for more context, or@clawsweeper stopto stop active automation.allenhurff commentedon Jun 21, 2026
Hey maintainers,
Following up with current user-impact context and linking the open fix path: PR #90407 (#90407) is still the clean/minimal fix candidate for this issue.
As of today, the latest published
@openclaw/memory-lancedbis2026.6.9, and it still declares:@lancedb/lancedb@0.30.0apache-arrow@21.1.0But
@lancedb/lancedb@0.30.0still peersapache-arrow >=15.0.0 <=18.1.0, so standard npm 11 resolution remains broken.This has now hit me across four consecutive OpenClaw updates, including
2026.6.9. My local repair path continues to restore thememory-lancedb@2026.5.28pin and keep LanceDB memory healthy, but that is now a recurring manual workaround for what feels like a core memory-stack component.The linked PR already makes the package-contract repair by pinning Arrow to
18.1.0and regenerating the graph files. From the latest review, the remaining path looks like either:memory-lancedb@2026.6.x.Happy to provide any extra logs or test a fixed package immediately after it is published. Thanks.