Check an upgrade against a recorded baseline
A pinned CLI and backup baseline exposed a real prerequisite: OpenClaw 2026.9.6 requires Node 24.16+ on the 24.x line or 26.1+. Package version and running gateway identity must be checked separately. No upgrade was performed.
- Published
- Oct 1, 2026
- Reviewed
- Oct 2, 2026
- Content updated
- Nov 13, 2026
- Applicable version
- OpenClaw 2026.9.6 baseline / Node.js 24.16.0; no upgrade run
- Platforms
- Current OpenClaw installation
Before you start
- A verified backup and permission to restart this instance
- A recorded harmless task baseline
The first round read the package engines, ran the 2026.9.6 CLI and staged backup restoration on two hosts. Windows global Node 24.15.0 falls below the declared minimum, so the trial used portable 24.16.0. Existing gateways were left running with their original runtime.
Prepare a comparison
- Record CLI version, running gateway identity, release channel and configuration paths. Do not include secrets in the shared record.
- Review the release notes relevant to your enabled channels and tools. Create and verify a backup before the change.
- Run five small baseline checks: text response, read-only file access, a fresh-session memory check, private test-channel reply and one harmless scheduled event.
- Follow the update method for your installation. Inspect completion and the actual running gateway version, then repeat the same checks.
First-round baseline and missing results
Package 2026.9.6, Node 24.16.0 and five-file staging restoration: checked on Windows x64 and macOS ARM64. Candidate version, update command, migration, actual gateway version before/after and the five Agent task checks: not run. Keep that distinction in a release decision; a passing backup cannot fill an empty regression column.
Acceptance
Compare outputs at each seam, not just the updater’s exit code. If a formerly passing task fails, keep the before/after versions, failure evidence and recovery files. Pause recurring tasks affected by the failure before they repeatedly act on incomplete output.
Recovery and cleanup
Use the current official recovery method for the recorded installation. Do not delete migration originals or backups until the baseline passes and intended data is present. Restoring code alone may not reverse a state migration.
Evidence and limits
Official documentation checked
A linked source changed and this record awaits editorial review. Check the original before relying on these steps. (12)
- Package engines and the pinned CLI backup baseline were checked. A candidate upgrade and actual gateway runtime comparison were not run.
- Chat, tools, fresh-session memory, messaging and scheduler regressions remain not run.
Evidence files
Sources
Cite or read with tools
https://botclaw.tech/items/wf-upgrade-regression