feat(kiloclaw): bump openclaw to version 2026.3.8#961
Open
kilo-code-bot[bot] wants to merge 1 commit intomainfrom
Open
feat(kiloclaw): bump openclaw to version 2026.3.8#961kilo-code-bot[bot] wants to merge 1 commit intomainfrom
kilo-code-bot[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 files)
|
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.
Summary
Bumps openclaw from
2026.3.2to2026.3.8inkiloclaw/Dockerfile.Verification
kiloclaw/Dockerfile(line 45)Visual Changes
N/A
Reviewer Notes
Potentially impactful changes from the v2026.3.8 release notes
Security hardening (review carefully):
Security/system.run: Approved
bunanddeno runscript operands are now bound to on-disk file snapshots at approval time, so post-approval script rewrites are denied before execution. If any workflows rely on modifying scripts between approval and execution, they will break.Browser/SSRF: Private-network intermediate redirect hops are now blocked in strict browser navigation flows, and the code fails closed when remote tab-open paths cannot inspect redirect chains. Could affect any browser-based tool usage that traverses private network redirects.
MS Teams/authz:
groupPolicy: "allowlist"now enforces sender allowlists even when a team/channel route allowlist is configured. If Teams integrations rely on route-level allowlists widening group access, this will tighten that behavior.Skills/download installs: The validated per-skill tools root is now pinned before writing downloaded archives, preventing path rebinding outside the intended tools directory. Could affect skill installation if any skills relied on non-standard paths.
Deployment/infrastructure changes:
Docker/runtime image: Dev dependencies are pruned and build-only dist metadata is stripped for smaller Docker images. This is a positive change but worth noting in case image size assumptions exist elsewhere.
Gateway/restart timeout recovery: The gateway now exits non-zero when restart-triggered shutdown drains time out, so systemd/launchd will restart it instead of treating a failed restart as a clean stop. This changes restart behavior — ensure our container orchestration handles non-zero exits as expected.
Gateway/config restart guard: Config is now validated before service start/restart, and post-SIGUSR1 startup failures no longer crash the gateway process. This reduces invalid-config restart loops. If we ever send SIGUSR1 for config reloads, behavior may differ on bad config.