feat(kiloclaw): bump openclaw to version 2026.6.9#4145
Draft
kilo-code-bot[bot] wants to merge 1 commit into
Draft
feat(kiloclaw): bump openclaw to version 2026.6.9#4145kilo-code-bot[bot] wants to merge 1 commit into
kilo-code-bot[bot] wants to merge 1 commit into
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
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
Bumps the packaged OpenClaw version in the KiloClaw image from 2026.6.8 to 2026.6.9: the
Dockerfile pin, the bundled plugin peer and dev deps, the lockfile, the e2e runbook version,
and a changelog entry. Prepared by automation.
Verification
Validate per the kiloclaw-openclaw-upgrade skill before marking this PR ready:
bash services/kiloclaw/scripts/tests/openclaw-upgrade-validate.sh— builds + keyless checks + grype CVE scan, then the credentialed live smoke (setKILOCODE_API_KEYfor the smoke).Visual Changes
N/A
Reviewer Notes
Automated upgrade assessment
Span: 1 release over 1 day (2026.6.8 to 2026.6.9).
Risk scores: Breaking changes Low, Security Low, Deployment Medium, Behavior Low, Span Low.
Recommendation: Review carefully.
This is a single same-day release. The notes are dominated by fixes and additive features with no breaking changes called out: richer Telegram delivery, more dependable agent recovery, a stronger Codex integration, and assorted channel and storage fixes. The security entries are hardening (redact secrets in debug and config output, block internal HTTP session overrides, audit open-DM tool exposure, retain plugin write ownership checks) and do not require action on our side.
Deployment is scored Medium because the release changes plugin loading and the bundled runtime deps install paths upstream: external provider packages become standalone npm releases, the gateway now discovers installed channel plugins at startup, and self-update avoids per-Node npm prefixes. Our image bakes bundled plugin runtime deps into the external stage dir whose naming mirrors OpenClaw's resolveExternalBundledRuntimeDepsInstallRoot, so the packaged image build and the live first-boot smoke are the right place to confirm the stage root still resolves and plugins load without an npm install on boot.
No injected instructions were found in the release body. Recommendation is capped at Review carefully because the image has not been built and the live smoke has not run; merging triggers the first production image build.