fix(node): bump Buzz-supplied Node runtimes past OpenClaw's >=24.15.0 floor - #3218
Merged
Conversation
wesbillman
approved these changes
Jul 27, 2026
… floor
A user reported all 10 ACP workers crashing on startup:
Buzz Node mismatch: Buzz supplies Node 24.14.0; OpenClaw requires
>=24.15.0. All 10 ACP workers immediately crash.
Buzz supplies Node to agent processes from two places, both stale:
- hermit dev environment pinned node 24.14.0 (the exact version in the
report — source/hermit builds). Bumped to 24.15.0, the newest version
hermit currently publishes, which satisfies OpenClaw's floor.
- the managed Node runtime shipped to Desktop users was even older
(v24.11.0). Bumped to v24.18.0 (current latest v24) with per-platform
SHA-256 digests taken from nodejs.org SHASUMS256.txt and re-verified
by downloading the darwin-arm64 artifact (hash match + extract +
node --version).
The managed runtime sits FIRST on the worker PATH
(managed_agents/runtime/path.rs), so a user-installed newer Node cannot
mask a stale managed one — the pin itself has to move.
All artifacts are within MANAGED_NODE_MAX_BYTES (largest 57 MB < 90 MB)
and the tar.gz layout keeps the node-vX-platform/bin/node shape
verify_node_tree expects (verified on darwin-arm64).
Co-authored-by: Tyler Longwell <tlongwell@block.xyz>
Signed-off-by: Tyler Longwell <tlongwell@block.xyz>
wpfleger96
approved these changes
Jul 27, 2026
tlongwell-block
force-pushed
the
eva/node-24-18-bump
branch
from
July 27, 2026 22:06
53e4dcf to
153bfb8
Compare
wesbillman
enabled auto-merge (squash)
July 27, 2026 22:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
User report:
Buzz supplies Node to agent processes from two places, and both were below OpenClaw's floor:
bin/.node-*.pkg) — the 24.14.0 in the report>=24.15.0)managed_node.rs/managed_node_paths.rs)The managed runtime sits first on the worker PATH (
managed_agents/runtime/path.rs), so a user-installed newer Node can't mask a stale managed one — the pin itself has to move.Verification
https://nodejs.org/dist/v24.18.0/SHASUMS256.txt; darwin-arm64 independently re-verified by downloading the tarball (hash match), extracting, and runningbin/node --version→v24.18.0.MANAGED_NODE_MAX_BYTES(largest linux-x64 at 57 MB < 90 MB cap); tar.gz layout keeps thenode-vX-platform/bin/nodeshapeverify_node_treeexpects.cargo test --libindesktop/src-tauri: 1801 passed, 0 failed at this commit;cargo fmt --check+cargo clippy --lib -D warningsclean.node --version == MANAGED_NODE_VERSION) makes upgrade automatic: installed v24.11.0 trees fail readiness and the installer stages v24.18.0 atomically (rename with.oldrollback — existing logic, unchanged).Note: CI
node-version: 24.14.1pins inrelease.yml/windows-canary.ymlare build-env only (already>=nothing OpenClaw touches) and left alone to keep this minimal.