Skip to content

chore(docker, openclaw): Updating openclaw to 2026.3.13 as per https:…#880

Open
buddingengineers12345 wants to merge 3 commits intoNVIDIA:mainfrom
buddingengineers12345:update-openclaw-in-docker
Open

chore(docker, openclaw): Updating openclaw to 2026.3.13 as per https:…#880
buddingengineers12345 wants to merge 3 commits intoNVIDIA:mainfrom
buddingengineers12345:update-openclaw-in-docker

Conversation

@buddingengineers12345
Copy link

@buddingengineers12345 buddingengineers12345 commented Mar 25, 2026

…//github.com//issues/328

To fix the issues mentioned in #328, the openclaw is getting updated

Summary

Related Issue

Changes

Type of Change

  • Code change for a new feature, bug fix, or refactor.
  • Code change with doc updates.
  • Doc only. Prose changes without code sample modifications.
  • Doc only. Includes code sample changes.

Testing

  • npx prek run --all-files passes (or equivalently make check).
  • npm test passes.
  • make docs builds without warnings. (for doc-only changes)

Checklist

General

Code Changes

  • Formatters applied — npx prek run --all-files auto-fixes formatting (or make format for targeted runs).
  • Tests added or updated for new or changed behavior.
  • No secrets, API keys, or credentials committed.
  • Doc pages updated for any user-facing behavior changes (new commands, changed defaults, new features, bug fixes that contradict existing docs).

Doc Changes

  • Follows the style guide. Try running the update-docs agent skill to draft changes while complying with the style guide. For example, prompt your agent with "/update-docs catch up the docs for the new changes I made in this PR."
  • New pages include SPDX license header and frontmatter, if creating a new page.
  • Cross-references and links verified.

Summary by CodeRabbit

  • Chores
    • Bumped the OpenClaw CLI version from 2026.3.11 to 2026.3.13 across build/runtime images, test suites, sandbox metadata, and verification flows. Tests and sandbox artifacts were updated to match the new CLI version. No functional changes to application behavior.

…#328

To fix the issues mentioned in NVIDIA#328, the openclaw is getting updated
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 25, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a99a63ab-1015-4c7e-8b2f-93338c4710f6

📥 Commits

Reviewing files that changed from the base of the PR and between ffd9f31 and e384155.

📒 Files selected for processing (1)
  • Dockerfile
✅ Files skipped from review due to trivial changes (1)
  • Dockerfile

📝 Walkthrough

Walkthrough

OpenClaw CLI version references were bumped from 2026.3.11 to 2026.3.13 across the Docker runtime image, package manifest, sandbox metadata, and related tests; no other logic, control flow, or public API declarations were changed.

Changes

Cohort / File(s) Summary
Runtime / Manifest
Dockerfile, package.json
Bump OpenClaw CLI from 2026.3.112026.3.13 (npm install -g openclaw@... and package.json).
Tests / Sandbox Metadata
test/Dockerfile.sandbox, test/e2e-test.sh, test/install-preflight.test.js
Update embedded OpenClaw metadata, test stubs, expected npm pack filename, and assertions from 2026.3.112026.3.13.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I nibbled lines with careful care,
Pushed a version up the stair.
Eleven hopped to thirteen bright,
Docker, tests, and manifest — all right.
A tiny carrot-coded delight! 🥕

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore(docker, openclaw): Updating openclaw to 2026.3.13' clearly summarizes the main change: a dependency version bump for openclaw across docker, package.json, and test files.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@Dockerfile`:
- Around line 71-72: Dockerfile currently pins openclaw@2026.3.13 while
package.json and test/install-preflight.test.js use 2026.3.11, causing
environment drift; fix by reconciling versions: either update package.json
dependency and the five literal fixtures in test/install-preflight.test.js to
2026.3.13 so scripts/install.sh (which derives the version from package.json)
and Dockerfile match, or refactor Dockerfile to accept a build ARG (e.g.,
OPENCLAW_VERSION) and use that arg in the RUN installing openclaw, then set that
ARG at build time to the version from package.json; ensure all references
(Dockerfile RUN installing openclaw, package.json dependency, and the five
fixtures in test/install-preflight.test.js) use the same canonical version
string.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a0d4f167-7db8-45a2-9ded-36ead8aa06e4

📥 Commits

Reviewing files that changed from the base of the PR and between 95fc7e2 and 39ef2d9.

📒 Files selected for processing (1)
  • Dockerfile

…#328

To fix the issues mentioned in NVIDIA#328, the openclaw is getting updated

updating multiple files
@buddingengineers12345
Copy link
Author

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@Dockerfile`:
- Around line 71-72: Dockerfile currently pins openclaw@2026.3.13 while
package.json and test/install-preflight.test.js use 2026.3.11, causing
environment drift; fix by reconciling versions: either update package.json
dependency and the five literal fixtures in test/install-preflight.test.js to
2026.3.13 so scripts/install.sh (which derives the version from package.json)
and Dockerfile match, or refactor Dockerfile to accept a build ARG (e.g.,
OPENCLAW_VERSION) and use that arg in the RUN installing openclaw, then set that
ARG at build time to the version from package.json; ensure all references
(Dockerfile RUN installing openclaw, package.json dependency, and the five
fixtures in test/install-preflight.test.js) use the same canonical version
string.

ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a0d4f167-7db8-45a2-9ded-36ead8aa06e4

📥 Commits
Reviewing files that changed from the base of the PR and between 95fc7e2 and 39ef2d9.

📒 Files selected for processing (1)

Fixed the review comments in the second commit

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.

2 participants