Description
When running the NemoClaw installer with NEMOCLAW_INSTALL_TAG=v0.0.56, the script completes successfully but the installed CLI is still nemoclaw v0.0.55, even though v0.0.56 is published as the latest release.
Environment
Device: DGX Spark / Ubuntu 24.04 server / MacBook Pro
OS: Ubuntu 24.04 / macOS / Windows WSL2
Architecture: x86_64 or arm64
Node.js: v22.22.3
npm: 10.9.8
Docker: Docker version 29.2.1, build a5c7197
OpenShell CLI: openshell 0.0.44
OpenClaw: OpenClaw 2026.5.22 (a374c3a)
NemoClaw: nemoclaw v0.0.55 (after attempted v0.0.56 install)
Steps to Reproduce
- Ensure any previous NemoClaw installation is removed, or that you are upgrading in place.
- Run the official installer with the tag pinned:
NEMOCLAW_INSTALL_TAG=v0.0.56 curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
- After the installer completes, open a new shell (if needed) and run:
- Optionally, re-run the installer command again to confirm the behavior is consistent.
Expected Result
- After the script finishes,
nemoclaw --version reports nemoclaw v0.0.56.
- If the installer cannot resolve or fetch v0.0.56 for any reason, it should fail with a clear non-zero exit code and a descriptive error (for example, "Requested tag v0.0.56 not available") rather than silently installing a different version.
Actual Result
- The installer completes without any obvious error or warning.
- Running
nemoclaw --version still reports nemoclaw v0.0.55 instead of v0.0.56.
- There is no message indicating that the requested tag was ignored or that the script fell back to v0.0.55; from the user's perspective, the tag appears to be accepted but is not actually applied.
Logs
- Terminal transcript of the installer run (stdout and stderr), especially any lines that mention the resolved NemoClaw version or install tag.
- Output of
nemoclaw --version before and after the install attempt.
Not captured.
Quick reference
- Component keyword:
NemoClaw_Install (and optionally NemoClaw_Upgrade if QE wants to track both new installs and upgrades).
- Severity: 3-Functionality — version pinning via
NEMOCLAW_INSTALL_TAG does not behave as advertised; users cannot reliably install the requested released version even when the tag exists.
Description
When running the NemoClaw installer with
NEMOCLAW_INSTALL_TAG=v0.0.56, the script completes successfully but the installed CLI is stillnemoclaw v0.0.55, even though v0.0.56 is published as the latest release.Environment
Steps to Reproduce
NEMOCLAW_INSTALL_TAG=v0.0.56 curl -fsSL https://www.nvidia.com/nemoclaw.sh | bashExpected Result
nemoclaw --versionreportsnemoclaw v0.0.56.Actual Result
nemoclaw --versionstill reportsnemoclaw v0.0.55instead ofv0.0.56.Logs
nemoclaw --versionbefore and after the install attempt.Not captured.
Quick reference
NemoClaw_Install(and optionallyNemoClaw_Upgradeif QE wants to track both new installs and upgrades).NEMOCLAW_INSTALL_TAGdoes not behave as advertised; users cannot reliably install the requested released version even when the tag exists.