Skip to content

fix: align channels and Node checks with OpenClaw - #23

Merged
PerfectPan merged 2 commits into
mainfrom
fix/openclaw-channel-node-alignment
Oct 31, 2026
Merged

PerfectPan merged 2 commits into
mainfrom
fix/openclaw-channel-node-alignment

Conversation

@PerfectPan

@PerfectPan PerfectPan commented Oct 31, 2026 •

Copy link
Copy Markdown
Owner

Motivation

OpenClaw now ships four release channels (stable, extended-stable, beta, dev) and requires Node 24.16+/26.1+ or 27+ (24.22.1+/26.12.1+ recommended, Node 24/26 prereleases rejected). ocvm only understood latest/stable, so extended-stable returned no rows and beta/extended-stable installs used the moving tag as the version directory. Version listing also sorted 2026.10.x against 2026.9.x lexicographically, and the Docker e2e image still ran Node 22, which upstream no longer supports.

Changes

  • Resolve latest, stable, beta, and extended-stable to concrete versions before install. stable prefers a stable dist-tag and falls back to latest; beta falls back to latest; extended-stable never falls back.
  • Add extended-stable labels to list-remote and sort remote/local versions with a numeric calendar-version comparator.
  • Add Node.js preflight warnings to install and failing doctor findings for unsupported runtimes (with a warning for versions below the recommended security patch level). Node 24/26 prereleases are rejected while Node 27+ dev labels remain accepted.
  • Move the Docker e2e image from Node 22 to Node 26.
  • Refresh README/site channel docs and clarify that snapshot/rollback only restore ocvm selection metadata, not OpenClaw SQLite state.

Validation

  • cargo fmt --check
  • cargo clippy --all-targets -- -D warnings
  • cargo test (6 unit + 6 CLI + 10 core tests)
  • cargo package --allow-dirty --offline
  • npm run build in site/
  • sh -n install.sh scripts/*.sh
  • ./scripts/check-release-prep.sh
  • Live npm smoke checks against openclaw:
    • list-remote --channel extended-stable -> 2026.9.36
    • list-remote --channel beta -> 2026.10.10-beta.5
    • default stable|beta|extended-stable resolved to 2026.10.9, 2026.10.10-beta.5, 2026.9.36
    • doctor with simulated Node 22 and Node 26.12.1-rc.1 reports the unsupported-runtime fix

./scripts/e2e-docker.sh was not run locally because Docker is unavailable on this machine; the updated E2E workflow runs Node 26 on this PR.

Risks / follow-ups

  • OpenClaw still shares one global SQLite state between versions; safely downgrading across schema migrations requires OpenClaw's own backup tooling. This PR documents that limitation rather than isolating state.
  • ocvm still does not install or pin Node.js; it only reports the current runtime.
  • OpenClaw's npm package is ~250 MB unpacked (~609 MB per installed version), so disk usage remains a follow-up.

- Resolve beta and extended-stable channels to concrete versions before install.
- Keep stable on the stable tag, falling back to latest when absent.
- Report unsupported or stale Node.js runtimes in install and doctor.
- Sort unpadded calendar versions numerically for list and list-remote.
- Move the Docker e2e image to Node 26.
@vercel

vercel Bot commented Oct 31, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
site Ready Ready Preview Oct 31, 2026 4:48am UTC

- Treat Node 24/26 prereleases as unsupported while accepting Node 27+ dev labels.
- Mention beta and extended-stable in the install help text.
- Document Node 27 and the prerelease rule in README and site install docs.
@PerfectPan
PerfectPan merged commit c82b0e8 into main Oct 31, 2026
10 checks passed
@PerfectPan
PerfectPan deleted the fix/openclaw-channel-node-alignment branch October 31, 2026 04:52
@PerfectPan PerfectPan mentioned this pull request Oct 31, 2026

This branch was successfully deployed

1 active deployment
Preview — dfbdf76d Deployed Oct 31, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant