Skip to content

feat(kiloclaw): bump openclaw to version 2026.6.6#3995

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

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

Conversation

@kilo-code-bot

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

Copy link
Copy Markdown
Contributor

Summary

Bumps the packaged OpenClaw version in the KiloClaw image from 2026.6.5 to 2026.6.6: 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 persisted-root live smoke: bash services/kiloclaw/scripts/controller-openclaw-upgrade-smoke-test.sh
  • 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

Scores: Breaking changes Low | Security Medium | Deployment Low | Behavior Medium | Span Low

Span: 1 release over 1 day (2026.6.5 to 2026.6.6).

Recommendation: Review carefully

This is a single same-day release that is dominated by security hardening. It tightens many
boundaries at once: transcripts, sandbox binds, host environment inheritance, MCP stdio, native
search policy, elevated sender checks, deleted-agent ACP paths, and loopback tools, and exec
approvals now fail closed on timeout. These are improvements, but tighter boundaries can change
runtime behavior, so this is scored Medium on Security and Medium on Behavior.

The config change most relevant to our integration is the openclaw config.patch update that makes
array replacement explicit and keeps indexed replacePaths consent from widening to whole arrays.
Our controller applies config by writing the openclaw.json file directly at boot rather than
driving the runtime config.patch RPC, so the direct impact on our integration is Low and breaking
risk is Low. Another notable behavior change is the default compaction timeout dropping to 180
seconds while still honoring explicit configuration.

No install, packaging, or deployment process changes were called out, so Deployment is Low. The
release body contained no injected instructions. The span is a single day, so Span is Low.

The recommendation is capped at Review carefully because the image has not been built and the live
persisted-root smoke has not been run; merging triggers the first production image build. Risk
flags: tighter security boundaries and exec fail-closed-on-timeout could surface behavior changes,
and the lowered compaction timeout default should be confirmed against expected workloads.

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