Repository navigation
chore(runtime): update OpenClaw to 2026.9.2 - #105
Merged
Merged
Conversation
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
1 participant
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.
Opened on behalf of Onur Solmaz (
osolmaz).Summary
MLClaw currently uses an older OpenClaw beta.
This change updates it to the latest stable OpenClaw release,
2026.9.2, and prepares MLClaw0.12.5.The official OpenClaw image supports AMD64 and ARM64, and the MLClaw integration tests pass against the published package.
What Changed
The release metadata now selects OpenClaw
2026.9.2.Generated release files and the bundled CLI now match MLClaw
0.12.5.Testing
The pinned OpenClaw integration test and the complete MLClaw quality gate passed under Node.js 24.
The official GHCR image was also verified for AMD64 and ARM64.
MLCLAW_OPENCLAW_PACKAGE_DIR=... npm test -- --run test/mlclaw.openclaw-integration.test.tsnpm run checkgit diff --checkdocker buildx imagetools inspect ghcr.io/openclaw/openclaw:2026.9.2Risks
This changes the embedded OpenClaw runtime across several upstream releases.
The published-package integration tests cover broker secret resolution and Telegram owner authorization, but the final GoEPT deployment still requires a real browser turn, Telegram startup check, and snapshot verification.