OpenClaw 2026.3.22 released with both a complete plugin-system failure and a WebUI crash. The follow-up 2026.3.23-2 patch failed to fix the plugin issue, forcing users to manually edit source code.
Version 2026.3.22 shipped with two unrelated but concurrent regressions. The plugin-system failure was caused by a packaging bug that omitted the web-components directory from the release artifact, meaning no installed plugin could be loaded. The WebUI crash stemmed from a missing null-check in the initial bootstrap path that threw an uncaught exception before render. Users who upgraded found themselves with a non-functional web interface and no working plugins — effectively a locked instance. The immediate patch 2026.3.23-2 fixed the WebUI but missed the packaging issue on plugins, requiring affected users to manually add the missing directory to their installation. Official guidance was 'do not upgrade to 2026.3.22' for two weeks.
The Actual Culprit
Release packaging excluded an entire directory due to a stale .npmignore entry. The packaging CI check did not verify that the resulting tarball contained the declared subdirectories.
CI that checks source-tree contents is not checking what users install. Unpack the published tarball and assert on its contents.
If a single null-check failure can kill the UI, every UI shell should have a render-fallback boundary, even (especially) in the bootstrap path.
Loading comments...