chore(image): promote Claude Code 2.1.226 after the canary passed
Canary first, production second — the point of pinning is that the upgrade is a decision, and the point of `canary-claude` is that the decision has evidence. Taken for 2.1.225's fix to a transient 401 that replaced a long-lived CLAUDE_CODE_OAUTH_TOKEN with a short-lived one and broke HEADLESS sessions until restart. Our sessions are headless and our VMs are per-mission, so "until restart" reads as a failed phase. The 2.1.225 workspace-trust prompt does NOT apply: `--help` states the dialog is skipped in non-interactive mode (`-p`, or stdout not a TTY) and we satisfy both. Read from the CLI in a booted 2.1.226 VM rather than inferred from the changelog. Verified on the production path after the rebuild: guest kernel 6.1.128, delegation to a subagent, `--settings` stop gate installed, judge independent (glm-4.7), single writer. 6/6. `rootfs-canary-claude.ext4` is left on tank as the mechanism for the next candidate, not as a leftover.
This commit is contained in:
@@ -27,7 +27,7 @@ FROM clawmates/agent-toolchain:dev
|
|||||||
# could undo. 2.1.221 also fixes `--mcp-config` servers not connecting before the
|
# could undo. 2.1.221 also fixes `--mcp-config` servers not connecting before the
|
||||||
# first turn in print mode, which is exactly the mode we run and will matter when
|
# first turn in print mode, which is exactly the mode we run and will matter when
|
||||||
# the MCP door reaches a VM.
|
# the MCP door reaches a VM.
|
||||||
ARG CLAUDE_CODE_VERSION=2.1.223
|
ARG CLAUDE_CODE_VERSION=2.1.226
|
||||||
RUN npm install -g "@anthropic-ai/claude-code@${CLAUDE_CODE_VERSION}" \
|
RUN npm install -g "@anthropic-ai/claude-code@${CLAUDE_CODE_VERSION}" \
|
||||||
&& npm cache clean --force \
|
&& npm cache clean --force \
|
||||||
&& rm -rf /root/.npm \
|
&& rm -rf /root/.npm \
|
||||||
|
|||||||
Reference in New Issue
Block a user