docs(reference): document OpenClaw build-time version pin (#2635)#3268
Merged
Conversation
Closes #2635 by documenting the existing build-time pin policy that satisfies the ticket's "OpenClaw version is pinned and documented in the release notes" acceptance criterion. The pin and detection machinery already exist; only the user-facing documentation was missing. The new "Checking the OpenClaw version" subsection under `nemoclaw <name> status` in commands.md explains: - OpenClaw is pinned at build time via `min_openclaw_version` in `nemoclaw-blueprint/blueprint.yaml`; the Dockerfile upgrades the cached base image to that version on rebuild. - Existing sandboxes do not auto-upgrade — users rebuild to pick up a newer pin. - `nemoclaw <name> status` prints the running OpenClaw version on the `Agent` line. - Stale sandboxes get an `Update` line in `status` and `connect` pointing at `nemoclaw <name> rebuild`. No code change. The build-time pin (Dockerfile:60-83), the version probe (src/lib/sandbox-version.ts), and the staleness warning wiring into status/connect/doctor (src/lib/actions/sandbox/status.ts:107 prints the Agent line; status/connect emit the staleness warning) are all on main today. Signed-off-by: Charan Jagwani <charjags100@gmail.com>
Contributor
|
ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughThis PR adds documentation describing how NemoClaw pins OpenClaw at sandbox build time, how to view the running OpenClaw version in ChangesOpenClaw Version Management Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Adds a Component Version Policy section to release-notes.md so the build-time pin choice for OpenClaw is captured in the literal location the #2635 acceptance criterion calls out (release notes), not just in the commands reference. The section links back to the full policy in docs/reference/commands.md to avoid duplicating the explanation. Signed-off-by: Charan Jagwani <charjags100@gmail.com>
ericksoa
approved these changes
May 8, 2026
ericksoa
left a comment
Contributor
There was a problem hiding this comment.
Reviewed current head e3a2938. The OpenClaw version-policy docs match the current implementation: blueprint.yaml and the OpenClaw manifest both pin 2026.4.24, Dockerfile upgrades stale base images during build from min_openclaw_version, and status/connect surface stale-version rebuild guidance. Docs dry-run and diff checks passed. Note: this PR is currently conflicting with main in docs/about/release-notes.md after the newer release-note section landed; resolve by keeping both sections before merge.
…rsion-policy # Conflicts: # docs/about/release-notes.md
miyoungc
added a commit
that referenced
this pull request
May 9, 2026
## Summary - Bump the docs release metadata to `0.0.38`. - Document release-prep updates for status policy versions, Local Ollama validation and cleanup, blueprint policy additions, rebuild backup handling, and NemoHermes uninstall branding. - Refresh generated `nemoclaw-user-*` skills from the updated docs. ## Source summary - #3185 -> `docs/reference/commands.md`: Documents that `nemoclaw <name> status` displays the gateway active policy version when OpenShell reports one. - #3167 -> `docs/reference/commands.md`, `docs/inference/use-local-inference.md`: Documents uninstall cleanup for matching Local Ollama auth proxy processes. - #2737 -> `docs/inference/use-local-inference.md`, `docs/network-policy/customize-network-policy.md`, `docs/manage-sandboxes/lifecycle.md`, `docs/reference/commands.md`: Documents stricter Local Ollama tool-call validation, blueprint policy additions, and partial rebuild backup handling. - #3220 -> `docs/reference/commands.md`: Documents NemoHermes-specific uninstall progress and completion text. - #3158 -> `.agents/skills/nemoclaw-user-configure-inference/*`: Refreshes generated user skills from existing `docs/inference/switch-inference-providers.md` heartbeat documentation. - #3199 -> `.agents/skills/nemoclaw-user-get-started/SKILL.md`: Refreshes generated user skills from existing `docs/get-started/quickstart.md` Model Router wording. ## Skipped - #3272 and #3268 were already documented by their merged docs updates on `main`. - #3154, #3216, #3166, and #3195 have no additional user-facing docs impact for this release-prep pass. - No commits matched `docs/.docs-skip`. ## Test plan - `python3 scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user` - `make docs` - `npm run build:cli` - Commit and pre-push hooks: markdownlint, docs-to-skills verification, gitleaks, commitlint, skills YAML tests, CLI typecheck Made with [Cursor](https://cursor.com) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Behavior Changes** * Rebuild now safely handles partial backups, preserving successfully captured entries while reporting only unarchived paths * Uninstall for Local Ollama setups now stops proxy processes before cleanup * Local Ollama models require stricter tool-call response validation during onboarding * Blueprint policy additions enable custom network policy extensions via `components.policy.additions` * New `NEMOCLAW_AGENT_HEARTBEAT_EVERY` configuration controls agent periodic task frequency * Status display now shows active policy version when available <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced May 14, 2026
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
4 participants
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.
Summary
Closes #2635 by documenting the existing build-time pin policy for OpenClaw inside the sandbox. The pin and detection machinery already exist — only the user-facing documentation was missing.
Related Issue
Closes #2635
What's already in main (no code change needed)
min_openclaw_version: "2026.4.24"innemoclaw-blueprint/blueprint.yaml. The Dockerfile (Dockerfile:60-83) upgrades the cached base image to that version on rebuild.src/lib/sandbox-version.tsSSHs into the sandbox, runs the agent's version command, caches the result in the registry.src/lib/actions/sandbox/status.ts:107printsAgent: OpenClaw v<version>innemoclaw <name> status.connectanddoctoremit a staleness warning pointing atnemoclaw <name> rebuildwhen the running version is older than the pin.What this PR adds
A new "Checking the OpenClaw version" subsection under
nemoclaw <name> statusindocs/reference/commands.mdthat explains:min_openclaw_versioninblueprint.yaml.statusprints the running version on theAgentline, and surfaces anUpdateline when stale.rebuildreuses the existing sandbox name and persisted credentials.Type of Change
Verification
npx prek run --all-filespasses (commit went through pre-commit hooks).docs/reference/commands.md.blueprint.yaml,Dockerfile,src/lib/sandbox-version.ts, andsrc/lib/actions/sandbox/status.ts.Summary by CodeRabbit
nemoclaw <name> statusand explains theAgentandUpdatelines.nemoclaw <name> rebuildto update the pinned version while retaining the sandbox name and credentials.