feat(kiloclaw): update OpenClaw to 2026.5.22 with live smoke#3502
Conversation
Sample live upgrade smoke run: OpenClaw 2026.4.23 -> 2026.5.22Captured from a disposable prospective The IMAGE_BEFORE=kiloclaw:release-check-before-2026.4.23 \
IMAGE_AFTER=kiloclaw:release-check-after-2026.5.22 \
EXPECTED_VERSION_BEFORE=2026.4.23 \
EXPECTED_VERSION_AFTER=2026.5.22 \
bash services/kiloclaw/scripts/controller-live-provider-smoke-test.sh --upgradeThis demonstrates persisted-root replacement compatibility, candidate doctor-path startup, explicit config validation, packaged Kilo Chat routing, Control UI proxying, and a real non-sensitive Auto Free turn through Kilo Gateway. |
|
Ok updated version with plugin diagnostics: |
…to-free-smoke # Conflicts: # apps/web/src/app/(app)/claw/components/changelog-data.ts # pnpm-lock.yaml
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryThe previously flagged Files Reviewed (1 file changed since last review)
Previously Reviewed Files (no changes)
Reviewed by claude-4.6-sonnet-20260217 · 147,255 tokens Review guidance: REVIEW.md from base branch |
Summary
2026.4.23to2026.5.22, align bundled Kilo Chat and Morning Briefing plugin dependencies, and add the user-facing release note.2026.5.22: target only the KiloCodeprovider-modelschunk because the newer release also contains a distinct DeepInfra discovery timeout.openclaw config validate --json, loads packaged Kilo Chat, inspects Kilo Chat plugin diagnostics, serves the proxied Control UI, and completes a real non-sensitive Auto Free turn through Kilo Gateway.origin/mainand committedHEADin isolated worktrees, reuses persisted/rootacross image replacement, executes the candidate's doctor/config-migration startup path, and asserts both installed OpenClaw versions.kiloclaw-openclaw-upgradeskill and validation checklist so future OpenClaw bumps repeat the persisted-root live checks, diagnostics review, bundle-patch investigation, and credential-safe reporting workflow.Verification
2026.5.22; the build confirmed the installed version and the scoped KiloCode discovery-timeout patch.2026.4.23to the checked-in2026.5.22candidate image. Both phases passed installed-version checks,openclaw config validate --json, controller/gateway readiness, proxied Control UI loading, packaged Kilo Chat loading and live webhook routing, and real Auto Free turns through Kilo Gateway (20 passed, 0 failed).origin/main, reran the official persisted-root upgrade wrapper with diagnostic-aware smoke coverage. The baseline reported no Kilo Chat diagnostics; the2026.5.22candidate surfaced the known cosmeticchannelConfigswarning; all functional checks passed (22 passed, 0 failed). Any additional or changed Kilo Chat diagnostic now fails the smoke.openclaw doctorreported no functional issues.Visual Changes
N/A
Reviewer Notes
pnpm-workspace.yamlexemptsopenclawfrom the dependency minimum-release-age rule because KiloClaw runtime images pin and explicitly live-smoke-test release candidates before rollout; this keeps plugin compile-time dependencies aligned with the validated image version.2026.5.22reports Kilo Chat as loaded inplugins inspectbut does not report the runtime route count from that standalone command. The semantic webhook request remains the authoritative no-side-effect proof that the live Kilo Chat handler is registered.openclaw plugins inspect kilo-chat --jsonis now parsed by the smoke test for diagnostics. The exact warning below is surfaced and temporarily allowed because it is cosmetic for the validated flow; any other Kilo Chat diagnostic fails smoke validation.openclaw doctoremits the same Kilo Chat diagnostic warning. This is non-blocking for the deployed KiloClaw flow validated here: Kilo Chat loads and its live route works, including end-to-end Telegram communication. Adding optional manifest metadata for OpenClaw setup/schema surfaces can be handled separately.