Skip to content

feat(kiloclaw): bump openclaw to version 2026.6.9#4145

Draft
kilo-code-bot[bot] wants to merge 1 commit into
mainfrom
feat/bump-openclaw-2026.6.9
Draft

feat(kiloclaw): bump openclaw to version 2026.6.9#4145
kilo-code-bot[bot] wants to merge 1 commit into
mainfrom
feat/bump-openclaw-2026.6.9

Conversation

@kilo-code-bot

@kilo-code-bot kilo-code-bot Bot commented Jun 21, 2026

Copy link
Copy Markdown
Contributor

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:

  • Run the local upgrade validation (one command): bash services/kiloclaw/scripts/tests/openclaw-upgrade-validate.sh — builds + keyless checks + grype CVE scan, then the credentialed live smoke (set KILOCODE_API_KEY for the smoke).
  • Run the skill's final submission gates (typecheck, tests, lint) and review plugin diagnostics.
  • Record the upgrade evidence (before and after versions, smoke result, any diagnostics) in this PR.
  • Mark this PR ready once the above pass.

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.

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