chore(sandbox): bump Claude Code 2.1.154 -> 2.1.223 - #1293
Open
lyoungblood wants to merge 1 commit into
Open
Conversation
The pinned CLI is ~2 months of releases behind npm latest. The image build already self-verifies the pin (claude --version | grep), and 2.1.223 installs and launches cleanly (verified locally via npm install + --version). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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 the sandbox image's pinned Claude Code CLI from
2.1.154(set in #272 for Opus 4.8 rendering) to the current npm latest2.1.223— the pin is roughly two months of releases behind.Verification
2.1.223installs and launches cleanly (npm install @anthropic-ai/claude-code@2.1.223→claude --version→2.1.223 (Claude Code)).claude --version | grep -F "${CLAUDE_CODE_VERSION}"), so a bad publish fails the build rather than shipping.Given the earlier stream-json/harness interaction incident (#903/#918/#921), you may want to run whatever harness-server validation you use for CLI bumps before merging — happy to help test on our deployment (we run the published images and validated per-turn
--modeloverrides end-to-end on the current image today).🤖 Generated with Claude Code