Repository navigation
fix: align channels and Node checks with OpenClaw - #23
Merged
Merged
Conversation
- 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.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- 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.
Merged
This branch was successfully deployed
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.
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).ocvmonly understoodlatest/stable, soextended-stablereturned no rows andbeta/extended-stableinstalls used the moving tag as the version directory. Version listing also sorted2026.10.xagainst2026.9.xlexicographically, and the Docker e2e image still ran Node 22, which upstream no longer supports.Changes
latest,stable,beta, andextended-stableto concrete versions before install.stableprefers astabledist-tag and falls back tolatest;betafalls back tolatest;extended-stablenever falls back.extended-stablelabels tolist-remoteand sort remote/local versions with a numeric calendar-version comparator.installand failingdoctorfindings 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.snapshot/rollbackonly restore ocvm selection metadata, not OpenClaw SQLite state.Validation
cargo fmt --checkcargo clippy --all-targets -- -D warningscargo test(6 unit + 6 CLI + 10 core tests)cargo package --allow-dirty --offlinenpm run buildinsite/sh -n install.sh scripts/*.sh./scripts/check-release-prep.shopenclaw:list-remote --channel extended-stable->2026.9.36list-remote --channel beta->2026.10.10-beta.5default stable|beta|extended-stableresolved to2026.10.9,2026.10.10-beta.5,2026.9.36doctorwith simulated Node 22 and Node 26.12.1-rc.1 reports the unsupported-runtime fix./scripts/e2e-docker.shwas not run locally because Docker is unavailable on this machine; the updated E2E workflow runs Node 26 on this PR.Risks / follow-ups
ocvmstill does not install or pin Node.js; it only reports the current runtime.