Repository navigation
[All Platforms][Regression] node version is not upgrading #2178
Description
Description
Description:
node version is not upgraded though the
Environment:- Platform: Brev
- NemoClaw: v0.0.20
Steps to Reproduce:
Pre-condition:
1. Machine with Node.js version < 22.16 (e.g. Node.js 20.x)
source "$HOME/.nvm/nvm.sh" && nvm install 20 && nvm use 20 && node --version && which node && npm --version
2. nvm installed
|
Actual:
labuser@2u1g-x570-0313:/mnt/c/Users/local-xiaomingh$ source "$HOME/.nvm/nvm.sh" && nvm install 20 && nvm use 20 && node --version && which node && npm --version Downloading and installing node v20.20.2... Downloading https://nodejs.org/dist/v20.20.2/node-v20.20.2-linux-x64.tar.xz... ###################################################################################################################################################################################################### 100.0% Computing checksum with sha256sum Checksums matched! Now using node v20.20.2 (npm v10.8.2) Now using node v20.20.2 (npm v10.8.2) v20.20.2 /home/labuser/.nvm/versions/node/v20.20.2/bin/node 10.8.2 labuser@2u1g-x570-0313:/mnt/c/Users/local-xiaomingh$ nvm --version 0.40.4 labuser@2u1g-x570-0313:/mnt/c/Users/local-xiaomingh$ npm --version 10.8.2 labuser@2u1g-x570-0313:/mnt/c/Users/local-xiaomingh$ node --version v20.20.2 labuser@2u1g-x570-0313:/mnt/c/Users/local-xiaomingh$ curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash ███╗ ██╗███████╗███╗ ███╗ ██████╗ ██████╗██╗ █████╗ ██╗ ██╗ ████╗ ██║██╔════╝████╗ ████║██╔═══██╗██╔════╝██║ ██╔══██╗██║ ██║ ██╔██╗ ██║█████╗ ██╔████╔██║██║ ██║██║ ██║ ███████║██║ █╗ ██║ ██║╚██╗██║██╔══╝ ██║╚██╔╝██║██║ ██║██║ ██║ ██╔══██║██║███╗██║ ██║ ╚████║███████╗██║ ╚═╝ ██║╚██████╔╝╚██████╗███████╗██║ ██║╚███╔███╔╝ ╚═╝ ╚═══╝╚══════╝╚═╝ ╚═╝ ╚═════╝ ╚═════╝╚══════╝╚═╝ ╚═╝ ╚══╝╚══╝ Launch OpenClaw in an OpenShell sandbox. v0.0.20 [1/3] Node.js ────────────────────────────────────────────────── [WARN] Node.js v20.20.2, npm major 10 found but NemoClaw requires Node.js >=22.16.0 and npm >=10 — upgrading via nvm… [INFO] nvm installer integrity verified ✓ Installing nvm... ✓ Installing Node.js 22... default -> 22 (-> v22.22.2) [INFO] Node.js installed: v22.22.2 [INFO] Runtime OK: Node.js v22.22.2, npm 10.9.7 [2/3] NemoClaw CLI ────────────────────────────────────────────────── [INFO] Installer payload is not a persistent source checkout — installing from GitHub… [INFO] Installing NemoClaw from GitHub… [INFO] Resolved install ref: latest ✓ Cloning NemoClaw source ✓ Preparing OpenClaw package ✓ Installing NemoClaw dependencies ✓ Building NemoClaw CLI modules ✓ Building NemoClaw plugin ✓ Linking NemoClaw CLI [INFO] Created user-local shim at /home/labuser/.local/bin/nemoclaw [INFO] Created user-local shim at /home/labuser/.local/bin/nemoclaw [INFO] Verified: nemoclaw is available at /home/labuser/.local/bin/nemoclaw ....... labuser@2u1g-x570-0313:/mnt/c/Users/local-xiaomingh$ node --version v20.20.2
Expect: Node is updated to latest >22.x
[NVB#6097713]
Activity
[-][NemoClaw][All Platforms][Regression] node version is not upgrading[/-][+][All Platforms][Regression] node version is not upgrading[/+]PrachiShevate-nv commentedon Apr 21, 2026
Reproduced on NemoClaw v0.0.21. Nvbug
fix(install): surface Node shell-reload requirement adjacent to insta…
fix(install): surface Node shell-reload hint adjacent to install line (…
Rohitkalidindi commentedon Apr 28, 2026
@cjagwani @ericksoa able to reproduce the issue with v0.0.28
Please reopen this issue
Below are steps
Rohitkalidindi commentedon May 8, 2026
@wscurran node version is not updated though install mentions it is upgraded
prekshivyas commentedon May 11, 2026
Stale-issue verification — automated
Reported on: v0.0.20
Verified on: v0.0.38 (current
latest)Verification mode: runtime reproduction on Brev
n2d-highmem-2— Node 20 pre-activated via nvm to mirror reporter's setup.Three empirical facts
node --versionaftersource "$NVM_DIR/nvm.sh" && nvm use 22)bash -lreads~/.bashrc→nvm.sh→ default alias 22)Why the same shell is unchanged
nvmis a shell function;install.shruns as a child process. The child'snvm use 22mutates its own subshell, which then exits — subprocess PATH changes cannot propagate to the parent. Unix process model, not a NemoClaw choice. Node 22 IS installed and set as default; workarounds #1 or #2 activate it. PR #2298 (v0.0.23, source has// See issue #2178.at the fix site) added the explicit hint, captured verbatim in our run.Asking the right person
@hulynn @Rohitkalidindi — when you ran
node --versionafter install and saw v20, did you also try one of:source "${NVM_DIR:-$HOME/.nvm}/nvm.sh" && nvm use 22in the same terminal, orBoth are verified to land at v22.22.2 above. If you tried either and it didn't work, please reopen with the output.
@cjagwani @PrachiShevate-nv — flagging for label decision. The bug-as-strictly-described is structurally unchangeable from a
curl | bashinstaller; PR #2298 is the team's best-available answer. Considerstatus: wont-fixif you agree.No label applied by this verification run.
wscurran commentedon May 13, 2026
@hulynn closing. See @prekshivyas comment above and re-open if this is still blocking QA.