Skip to content

chore: bump Claude Code 2.1.245 -> 2.1.246 - #22

Merged
intech merged 1 commit into
mainfrom
feat/bump-claude-code-2.1.246
Aug 25, 2026
Merged

chore: bump Claude Code 2.1.245 -> 2.1.246#22
intech merged 1 commit into
mainfrom
feat/bump-claude-code-2.1.246

Conversation

@intech

@intech intech commented Aug 25, 2026

Copy link
Copy Markdown
Member

Follow-up to #21: 2.1.246 became the npm latest dist-tag a few hours after
that PR pinned 2.1.245 (published 2026-08-25T19:17Z). engines.node >= 22.0.0
is satisfied by the base — the image runs Node v22.22.3.

Change

  • tools/package.json: pin 2.1.245 -> 2.1.246
  • tools/package-lock.json: regenerated inside node:22. The diff touches
    only claude-code and its eight platform packages.
  • npm audit: unchanged — the same two pre-existing high-severity findings
    (perplexity-mcp -> @modelcontextprotocol/sdk, GHSA-w48q-cv73-mx4w, "No
    fix available").

Size: the image shrinks 2.11 -> 1.84 GiB

@anthropic-ai in node_modules drops 743 -> 468 MB, moving the npm ci
layer 1132.0 -> 856.9 MB. Measured across three builds, the claude-code share
swings widely between patch releases — 641 MB at 2.1.238, 743 MB at 2.1.245,
468 MB at 2.1.246 — so CLAUDE.md now says to re-measure after a bump rather
than carry the previous number over.

Verification (freshly built amd64 image, production profile)

Run under --cap-drop=ALL, --security-opt=no-new-privileges,
--pids-limit=100, tmpfs HOME, host uid:

  • claude --version -> 2.1.246 (Claude Code)
  • claude doctor -> No installation issues found. (only the expected Remote
    Control full-scope-token caveat)
  • claude mcp list -> all six servers connected under the default
    MCP_TIMEOUT=10000 on three consecutive runs; 4.1s median (4.0-4.2s),
    down from ~6.9s on 2.1.245
  • claude --help still lists every flag the entrypoint passes:
    --remote-control, --remote-control-session-name-prefix,
    --dangerously-skip-permissions

Documentation

CLAUDE.md and README.md version mentions updated; the claude doctor
observation is relabelled 2.1.246, and the health-check and layer/image sizes
are replaced with this run's measurements.

2.1.246 became the npm latest dist-tag a few hours after #21 pinned
2.1.245. Same procedure: pin edited in tools/package.json, lockfile
regenerated inside node:22. The diff touches only claude-code and its
eight platform packages, and npm audit is unchanged (the same two
pre-existing high-severity findings in perplexity-mcp ->
@modelcontextprotocol/sdk, no fix available).

engines.node >=22.0.0 is satisfied by the base (Node v22.22.3 in the image).

Verified on the freshly built amd64 image under the production profile
(cap-drop=ALL, no-new-privileges, --pids-limit=100, tmpfs HOME, host uid):
claude --version reports 2.1.246, claude doctor reports "No installation
issues found." (only the expected Remote Control full-scope-token note),
all six MCP servers connect under the default MCP_TIMEOUT=10000 on three
consecutive runs, and claude --help still lists every flag the entrypoint
passes (--remote-control, --remote-control-session-name-prefix,
--dangerously-skip-permissions).

The image shrinks 2.11 -> 1.84 GiB: @Anthropic-AI in node_modules drops
743 -> 468 MB, moving the npm ci layer 1132.0 -> 856.9 MB. Measured across
three builds the claude-code share swings widely between patch releases
(641 MB at 2.1.238, 743 MB at 2.1.245, 468 MB at 2.1.246), so CLAUDE.md now
says to re-measure after a bump rather than carry the number over.

MCP startup also got faster: claude mcp list is ~4.1s wall-clock (median of
3 runs, 4.0-4.2s) against ~6.9s on 2.1.245, still all six servers connected.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@intech intech self-assigned this Aug 25, 2026
@intech
intech merged commit 4958b7d into main Aug 25, 2026
3 checks passed
@intech
intech deleted the feat/bump-claude-code-2.1.246 branch August 25, 2026 23:42
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.

1 participant