Repository navigation
Conversation
Moves OpenClaw and the first-party plugins in lockstep from 2026.8.35 to 2026.9.37, the extended-stable line. The ACP backend plugin now resolves smol-toml 1.9.0, clearing GHSA-r4xh-jqrq-34v2. The acpx CLI stays 0.21.1, so the ACP worker adapter ranges (already aligned with its built-ins) are unchanged. 2026.9.37 requires `>=24.22.1 <25 || >=26.12.1`: Node 22 and 25 are no longer supported. - platform_compat mirrors the new per-line floors; bootstrap provisions the NodeSource channel of the floor's release line instead of 22.x - CI smoke and memory-plugin matrices on 24.22.1/26.12.1; fresh-host and the lock toolchain on Node 24.22.3 / npm 11.19.1 - floor contract checks every supported line's floor, not just Node 22 - dependabot holds the 2026.9 line (ignore >=2026.10.0) - overrides: undici 8.12.4 dropped (2026.9.37 bundles its own undici, which overrides cannot reach); npm pinned to 11.21.2 so the npm CLI OpenClaw now depends on carries undici 6.29.1 instead of 6.28.0 Known residual: OpenClaw 2026.9.37 bundles undici 8.10.2, inside advisories fixed in 8.12.2 (e.g. GHSA-4w7w-5xrc-9h26). No later 2026.9 release exists to pick up the fix. BREAKING CHANGE: Node 22.x and 25.x hosts are refused; Node 24.22.1+ or 26.12.1+ is required.
The macos-15-intel image ships Node.js 22.23.2 in /usr/local/bin, which the fresh-host scenario resolves first. Under the new 24.22.1 floor that Node is refused, bootstrap falls back to `brew install node`, and Homebrew publishes no Intel macOS bottles for any Node formula, so the fresh-host macOS jobs and the Feature Verification macOS lane fail before setup. Both lanes now install the official nodejs.org package (pinned version and SHA-256) into /usr/local first, the same path an Intel operator takes. The new `hosted_docker.py install-node` helper refuses versions outside the supported range and checks the installed binary's version.
The healthcheck steps ran with the workflow runner's 30s shell default. On OpenClaw 2026.9.37 `openclaw doctor` alone takes 20-27s on an idle host with a bare config, so the step timed out on a provisioned host (Feature Verification run 44223925453), and the deep security audit was close to the limit too. Setup already gives doctor 300s.
…ehaviour - fake model: read the latest user *turn* (consecutive user messages). 2026.9 appends per-request runtime context as its own trailing user message, so the prompt's echo token was lost and agent/ACP turns replied "acknowledged" - FeatureHost: retry openclaw and gateway admin calls while OpenClaw answers with its explicit "retry" refusals (state store in offline maintenance, session storage not ready) during gateway startup, bounded to 180s - node-tools unit test: record only the module's own retry sleeps; patching the global time.sleep also captured subprocess's wait-poll backoff, which made the test (and `clawops baseline verify`) flaky
`model-auth ensure` gave `openclaw agents list` 30s, and the other read-only queries 10-60s. In isolation, 2026.9.37 runs these about twice as long as 2026.8.35 (`agents list --json`: 2.0-3.9s -> 4.8-6.4s on a bare config). On the Intel macOS host, right after setup, the queries also share the CPU with a Gateway that took 64s to start. `agents list` hit its 30s limit there, ensure exited 1 before applying the model chain, and the agent stayed on the profile default model (Feature Verification run 44231180562). The read-only queries now share one 120s budget, the same budget as the inference probe.
`memory verify-pro-parity --mode openclaw` gave `openclaw memory-pro search` 30s. On OpenClaw 2026.9.37 the CLI was still loading the memory-lancedb-pro plugin when that limit hit (Feature Verification run 44235709488, linux-lancedb), so the live side came back empty and the parity check failed. The search now gets the same 120s as the module's memory-pro import.
`_session_reply` accepted the session's latest assistant message when it was no more than 1s older than the send. In Feature Verification run 44240797608, `/acp spawn` was answered less than 1s before `/acp steer` was sent, so the spawn confirmation was read back as the steer reply. A reply must now also be newer than the session's latest message from before the send.
2026.9.37 bundles undici 8.10.2, inside high advisories fixed in 8.12.2 (GHSA-4w7w-5xrc-9h26), and no later 2026.9 release exists. 2026.11.5 no longer bundles undici: it resolves undici 8.12.3, and the first-party plugins resolve smol-toml 1.9.1. - openclaw and the first-party plugins move to 2026.11.5 in lockstep; the acpx CLI stays 0.21.1 - Node floors follow its engines, `>=24.16.0 <25 || >=26.1.0`; CI floor legs are 24.16.0 / 26.1.0, and docs name the 24.22.1 / 26.12.1 security releases OpenClaw recommends - dependabot holds the 2026.11 line (ignore >=2026.12.0); its contract derives the bound from the pinned CalVer month - overrides: npm 12.2.2 (OpenClaw pins npm 12.2.0, which bundles undici 6.28.0; 12.2.2 bundles 6.29.1), and @hono/node-server 2.1.8, main's version. The exact @modelcontextprotocol/node 2.1.1 pin otherwise forces a 1.x copy inside GHSA-rmxm-3fg6-px4f; upstream 2.1.2 accepts ^2.1.3 - the FV retry seam matches 2026.11's wording: offline maintenance with owner details, schema admission, and "agent store is ready" 2026.11.5 was published 2026-11-17, inside the updater's 3-day release quarantine. The pin was taken by owner decision. Every other new or changed package was then re-resolved with the quarantine on, so the only packages under 3 days old are OpenClaw 2026.11.5's own. BREAKING CHANGE: Node 22.x and 25.x hosts are refused; Node 24.16.0+ or 26.1.0+ is required.
OpenClaw 2026.11 CLI commands print a Node process warning on stderr as
they exit ("Plugin source receipt was not recorded: Gateway is closing;
plugin shared-state admission is closed"). The vendored host test merges
both streams for plain output, so `memory-pro version` no longer matched
the package version exactly on either Node line. Its log filter now drops
`(node:<pid>)` warning lines along with plugin logs.
`openclaw config validate` on 2026.11.5 rejects three keys the baseline and channels overlays render, which failed `clawops doctor-host` on fresh hosts: - agents.defaults.heartbeat: monitors are now ordinary automation jobs. The baseline only used the key to switch heartbeat off. 2026.11 provisions a Proactive check job only from an explicit `openclaw setup`, which StrongClaw never runs, so no periodic check exists without it. - channels.defaults.heartbeatVisibility: it moved into each migrated automation's delivery policy. - skills.workshop.approvalPolicy: Skill Workshop proposals were removed. All six render profiles now pass 2026.11.5 `config validate`. The feature test for overlay merging now changes a nested `subagents` key instead of the retired `heartbeat` one.
OpenClaw 2026.11 moved its default agent sandbox image from
`openclaw-sandbox:bookworm-slim` to `openclaw-sandbox:trixie-slim`, and
fails sandboxed turns when it is missing ("Sandbox image not found"). In
Feature Verification run 44275092875 that failed every agent turn.
StrongClaw now builds the new tag from upstream's documented recipe (the
same packages, user and command) on a digest-pinned `debian:trixie-slim`
index.
The unsandboxed `acp-dispatch` agent relied on OpenClaw stopping any turn whose explicit tool allowlist leaves no callable tool. It used `allow: [session_status]` plus `deny: ["*"]`. OpenClaw 2026.11 treats a `*` deny as "tools disabled", enforces only runtime allowlists in that case, and runs the turn tool-less. An ordinary message to the dispatcher reached the model (Feature Verification run 44275092875). Probed in isolation with `openclaw agent --local` on 2026.11.5: - allow session_status + deny "*": the provider replied - allow session_status only: the provider replied - allow only a tool nothing registers, no deny: "No callable tools remain", and the provider was never contacted The dispatcher now allows only `strongclaw_dispatcher_has_no_tools`, with no `*` deny. The sandbox contract pins that sentinel and rejects a `*` deny.
OpenClaw 2026.11 runs `openclaw memory status|index|...` only while no
Gateway owns the state directory ("This command is offline-only"). The
deep `clawops doctor` and `clawops baseline verify` ran `memory status
--deep` against a live Gateway.
`run_openclaw_memory_status` runs the documented offline check, and on
that refusal asks the Gateway for the same deep check through
`gateway call doctor.memory.status {"deep":true}` (operator.read). Any
other failure is reported as before. The runner is injected, so callers
keep their existing test seams.
The profile feature tests run their offline-only `memory status` and
`memory index` inside a new `GatewayController.offline()` window, which
stops and restarts the systemd, launchd or harness gateway as an
operator would.
The deep doctor test reported the first 600 chars of each failed check. On OpenClaw 2026.11 that space fills with plugin registration log lines, hiding the error itself. It now drops `[plugins]` log lines and keeps the last 600 chars.
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
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.
Summary
Moves the node-tools bundle from OpenClaw 2026.8.35 to 2026.11.5 (dist-tag
latest) and drops Node 22, by owner decision.This PR first targeted 2026.9.37 (extended-stable). That release bundles undici 8.10.2, inside high advisories fixed in 8.12.2 (GHSA-4w7w-5xrc-9h26), and no later 2026.9 release exists. 2026.11.5 has neither problem:
Other details:
@openclaw/*plugins move in lockstep. The lock was regenerated withtests/scripts/update_node_tools_lock.py(npm cismoke) and mirrored intosrc/clawops/assets/.@openclaw/acpxembeds 0.21.0), so the ACP worker adapter ranges are unchanged.openclaw,@openclaw/*).Node support
2026.11.5
engines.nodeis>=24.16.0 <25 || >=26.1.0. Itsnode-version.mjsalso names 24.22.1 / 26.12.1 as strongly recommended security releases.platform_compat.NODE_RELEASE_FLOORSsetup_22.x(hard-coded)setup_24.x)/usr/local, through the newhosted_docker.py install-node. Two things required this:macos-15-intelimage ships Node 22.23.2, which the new floor refuses.brew install nodefallback fails there.Dependabot
openclaw/@openclaw/*ignore>=2026.12.0, which holds the pinned 2026.11 line. The contract test derives the bound from the pinned CalVer month.npm overrides
undici: 8.12.4. The tree resolves patched undici 8.12.3 directly.npm: 12.2.2. OpenClaw pinsnpm@12.2.0, which bundles undici 6.28.0. 12.2.2 bundles undici 6.29.1.@hono/node-server: 2.1.8. This is the versionmainalready locks.@modelcontextprotocol/node@2.1.1, which accepts only^1.19.9. Every 1.x from 1.19.10 is inside GHSA-rmxm-3fg6-px4f.@modelcontextprotocol/node@2.1.2widens that to^1.19.9 || ^2.1.3. Overriding that package instead would break OpenClaw's exact@modelcontextprotocol/server@2.3.1pin, since 2.1.2 needs^2.4.0.OpenClaw 2026.9+ behaviour adaptations (re-verified on the 2026.11.5 dist)
agent:<harness>:acp:<uuid>, and steer replies are still truncated at 800 chars.FeatureHostretries OpenClaw's explicit "retry" refusals during Gateway startup, within 180s. The pattern now covers 2026.11's wording:openclaw doctortakes 20–27s idle.memory-pro searchused byverify-pro-paritygets 120s.time.sleep._session_replycould read back the previous command's reply.OpenClaw 2026.11 breaking changes absorbed
Each item below was found by CI or Feature Verification, then confirmed in the 2026.11.5 dist or its shipped docs.
config validaterejectsagents.defaults.heartbeat,channels.defaults.heartbeatVisibilityandskills.workshop.approvalPolicy, so these are removed.heartbeatto turn monitoring off.openclaw setup, which StrongClaw never runs, so no periodic monitor exists.config validateon 2026.11.5.openclaw-sandbox:trixie-slim; sandboxed turns fail fast without it.clawopsnow builds upstream's recipe on a digest-pinneddebian:trixie-slim.tools.deny: ["*"]as "tools disabled" and runs the turn tool-less. The oldallow: [session_status]+deny: ["*"]let an ordinary message to the unsandboxedacp-dispatchagent reach the model.*deny. OpenClaw then refuses the turn with "No callable tools remain", verified withopenclaw agent --localagainst the fake provider.memory statusis offline-only while a Gateway owns the state.clawops doctorandbaseline verifynow run the offline check and, on that refusal, ask the owning Gateway (gateway call doctor.memory.status {"deep":true},operator.read).memory status/memory indexinside aGatewayController.offline()window.(node:<pid>)lines like plugin logs.Remaining advisories in the locked tree (
npm audit, root causes)<= 4.0.7)main) + npm's bundled 10.2.5Notes on this table:
npm auditreports 32 entries; the high-severity ones other than picomatch are npm's bundled internals inheriting GHSA-fc5q.mainreports 8 moderate: minimatch, plus smol-toml, which this PR clears.Other notes
lossless-claw(pinned v0.3.0) logs "runtime is intentionally unavailable during cli-metadata registration" on every 2026.11 CLI command. It is not fatal: CLI commands and Feature Verification pass. Upstream v1.2.0 declares CLI metadata but only claims tests against 2026.9.x, so it is left for a separate change.plugins.load.paths; it logs "only bundled plugins can claim reserved command ownership". Installing it throughopenclaw plugins install(as is already done for acpx) is the likely follow-up.Verification
Local runs, raw:
pytest -m "unit or contract": 1646 passed.openclaw config validateon 2026.11.5.CI on
e16ddac: all required checks pass (Verdict run 44288106963, Attribution Guard run 44288106812). That is 21 pass, 3 skipped by path filters. One macOS fresh-host job hit its 35-minute step cap while setup was still progressing, with no hang signature. The single allowed re-run (attempt 2) passed.Feature Verification run 44288116824 on
e16ddac: 93 PASS / 0 FAIL / 9 UNVERIFIABLE. This matches themainbaseline (run 44107296257), with no per-feature verdict changes.