Summary

After upgrading OpenClaw from 2026.5.28 to 2026.6.1, the @openclaw/[email protected] 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.5 arm64
• 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/[email protected]
npm error Found: [email protected]
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/[email protected]
npm error node_modules/@lancedb/lancedb
npm error @lancedb/lancedb@"0.30.0" from the root project

Observed Result

• Core OpenClaw upgrade succeeds.
• memory-lancedb update fails.
• OpenClaw disables memory-lancedb in 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 [email protected] extension remains physically installed and the LanceDB store is still readable.

Expected Result

@openclaw/[email protected] should install cleanly under npm 11, or its package dependencies should align with the peer dependency declared by @lancedb/[email protected].

Specifically, either:

• do not require [email protected] while using @lancedb/[email protected], 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 [email protected] plugin in config, rather than forcing npm with --force or --legacy-peer-deps.