Skip to content

chore(deps): bump bundled agents to latest - #945

Open
dohooo wants to merge 21 commits into
mainfrom
automation/bump-bundled-vendors
Open

chore(deps): bump bundled agents to latest#945
dohooo wants to merge 21 commits into
mainfrom
automation/bump-bundled-vendors

Conversation

@dohooo

@dohooo dohooo commented Jul 25, 2026

Copy link
Copy Markdown
Owner

Automated daily bundled-agent version sweep. Brings the in-scope bundled coding agents up to their latest stable upstream releases. This is the rolling automation PR — bumps accumulate here until merged.

Vendor bumps (vs main)

Vendor Current (main) Target Notes
@anthropic-ai/claude-code 2.1.219 2.1.239 staged binary; SHA256 (arm64+x64) added
@anthropic-ai/claude-agent-sdk 0.3.219 0.3.239 lockstep with claude-code (claudeCodeVersion: 2.1.239 ✓)
@openai/codex 0.145.0 0.149.0 staged binary; SHA256 (arm64+x64) added; layout descriptor layoutVersion: 1 unchanged
@cursor/sdk 1.0.24 1.0.28 class-A npm SDK (no SHA); Node ≥22.13 floor met by bundled Node 24; @connectrpc/connect-node resolves ✓; already latest
@opencode-ai/sdk 1.18.4 1.18.21 SDK + CLI lockstep
opencode-ai 1.18.4 1.18.21 staged binary; SHA256 (arm64+x64) added
Kimi 0.29.1 0.38.0 GitHub-release binary; SHA256 (darwin+win32 × arm64+x64) added

All in-scope vendors are at their latest stable upstream release (re-checked live 2026-08-22: claude-code/agent-sdk latest = 2.1.239 / 0.3.239, codex 0.149.0, cursor 1.0.28, opencode 1.18.21, Kimi via @moonshot-ai/kimi-code npm latest = 0.38.0).

CI toolchain fix (unrelated to the bumps — flagged for visibility)

CI's Clippy runner advanced to rustc 1.98.0, which enables the clippy::chunks_exact_to_as_chunks lint. Under -D warnings it now hard-fails on pre-existing code in src/slack/desktop_scrape.rs:359 (.chunks_exact(2)) — a file byte-identical to main and untouched by this PR (last changed in #882). This lint fails on main too under the same updated toolchain, so it is not caused by the vendor bumps. Rather than leave this rolling PR red indefinitely, I applied the exact compiler-suggested, behavior-identical rewrite (as_chunks::<2>().0.iter()) in commit b1d239e. as_chunks is stable since Rust 1.88; CI uses 1.98. You may prefer a dedicated fix on main — happy to drop this commit if you land that separately.

Files touched

  • sidecar/package.json — version pins (claude 2.1.239 / 0.3.239, codex 0.149.0, opencode 1.18.21)
  • sidecar/scripts/vendor-platform.tsCLAUDE_CODE_SHA256["2.1.239"], CODEX_SHA256["0.149.0"], OPENCODE_SHA256["1.18.21"] (arm64+x64), KIMI_VERSION0.38.0 + KIMI_SHA256["0.38.0"] (4 platforms). Cursor is class-A (no SHA table).
  • sidecar/bun.lock — regenerated
  • .changeset/bump-bundled-agents.md — single rolling patch changeset
  • src-tauri/src/slack/desktop_scrape.rs — clippy as_chunks fix (see CI toolchain fix above)

Local verification gates (latest revision — claude 2.1.239 / codex 0.149.0 / opencode 1.18.21 / Kimi 0.38.0)

Gate Result
bun install ✓ versions resolved; Claude lockstep verified (agent-sdk 0.3.239 ↔ claudeCodeVersion 2.1.239); cursor Node ≥22.13 floor met by bundled Node 24; @connectrpc/connect-node present; --frozen-lockfile clean
bun run typecheck ✓ exit 0 — no SDK export/type breaks
bun test ✓ 418 pass, 1 skip, 0 fail
cargo test --test pipeline_scenarios --test pipeline_fixtures --test pipeline_streams ✓ pass (119 fixtures + 1 stream + scenarios), 0 fail — stdout event-shape contract intact
cargo clippy --lib ✓ the as_chunks fix compiles cleanly (verified locally on Linux; the exact failing lint is toolchain-1.98-only, but the rewrite is the compiler's own suggestion and behavior-identical)
SHA256 ✓ claude 2.1.239 + codex 0.149.0 + opencode 1.18.21 computed from the exact npm tarball URLs (npm_vendor_sha.sh); Kimi 0.38.0 computed by downloading the exact release-zip URLs (arm64+x64 × darwin/win32)

Breaking-change assessment

All vendor bumps are patch/minor increments. typecheck (SDK export/type break detector) and the Rust pipeline snapshot tests (stdout event-shape contract) pass, so no Helmor-affecting breaking changes detected in the npm vendors. Codex stays within the 0.14x line (patch 0.148 → 0.149); layout descriptor expected to remain layoutVersion: 1 (verified on CI's cross-arch build). Kimi is a staged GitHub-release binary (not an npm dep), affecting only the staging/SHA path; its hard-enforced ACP protocol version (ACP_PROTOCOL_VERSION) has historically been stable across patch/minor releases and cannot be runtime-smoke-tested in this Linux sandbox (Kimi ships darwin/win32 binaries only). If it changed, the ACP handshake would throw at connect time rather than corrupt silently — worth a manual kimi acp smoke-test before merge.

Update bundled coding agents to their latest stable releases:
- Claude Code 2.1.219 -> 2.1.220 (claude-agent-sdk 0.3.219 -> 0.3.220, lockstep)
- OpenCode 1.18.4 -> 1.18.5 (sdk + cli)

Cursor SDK (1.0.24), Codex (0.145.0) and Kimi (0.29.1) already current.

Gates passed: bun install (lockstep verified 0.3.220 <-> claudeCodeVersion
2.1.220), typecheck, bun test (418 pass), cargo pipeline tests
(scenarios/fixtures/streams all green).

Claude-Session: https://claude.ai/code/session_01R2BguwSr4EeZeUXWYokSxs
@vercel

vercel Bot commented Jul 25, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
helmor-marketing Ignored Ignored Preview Aug 22, 2026 2:25am

Request Review

claude added 20 commits July 28, 2026 02:15
Add OpenCode 1.18.7 (SDK + CLI lockstep, arm64+x64 SHA256) and Kimi 0.29.2
(four-platform SHA256) on top of the existing Claude 2.1.220 bump in this
rolling automation PR.

Claude-Session: https://claude.ai/code/session_01A5pmMN6R6tJVV6JJpiTZeB
Latest stable moved 1.18.7 -> 1.18.8 (SDK + CLI lockstep). Gates:
typecheck, sidecar tests (418 pass), pipeline snapshots (119+1) all green.

Claude-Session: https://claude.ai/code/session_014Txgp4czxAj13Cf6d9qKAV
Codex 0.145.0 -> 0.146.0, Cursor SDK 1.0.24 -> 1.0.26, OpenCode
1.18.8 -> 1.18.10 (SDK+CLI), Kimi 0.29.2 -> 0.31.0. Claude Code
2.1.220 / agent-sdk 0.3.220 already current.

Claude-Session: https://claude.ai/code/session_01RzWH6K1fqayn8N2hpXL4M9
Latest stable Kimi release (npm `@moonshot-ai/kimi-code@latest` = 0.31.1).
SHA256 for all four platform assets sourced from the release `.zip.sha256`
sidecars. Other in-scope agents already at latest on this branch.

Claude-Session: https://claude.ai/code/session_016DqQHMMpzbJot3SMqhEGBk
Advance the rolling vendor bump to the newest stable upstream since the
last update:
- @anthropic-ai/claude-code 2.1.220 -> 2.1.221 (+ SHA256 arm64/x64)
- @anthropic-ai/claude-agent-sdk 0.3.220 -> 0.3.221 (lockstep, claudeCodeVersion 2.1.221)
- @opencode-ai/sdk + opencode-ai 1.18.10 -> 1.18.12 (+ SHA256 arm64/x64)

Codex 0.146.0, Cursor SDK 1.0.26, Kimi 0.31.1 already at latest.

Claude-Session: https://claude.ai/code/session_01H8JFeY2NSVN4BkQoqi9RKE
Kimi 0.31.1 -> 0.32.0 (latest stable). SHA256 for all four platforms
(darwin/win32 x arm64/x64) sourced from the release .zip.sha256 sidecars
and verified by direct download + shasum.

Claude-Session: https://claude.ai/code/session_01JbhKQPG7VXmeuNb2VSnLQz
All other in-scope vendors already current (codex 0.147.0, cursor 1.0.27,
opencode 1.18.14, kimi 0.34.0).

Claude-Session: https://claude.ai/code/session_01MG9L5MgQhvBvNtHmM2oKuP
All in-scope vendors already at latest stable; previous CI run was
cancelled. Empty commit to re-run the pipeline to green.

Claude-Session: https://claude.ai/code/session_01TGVD6FL12ixvZYJrSf5UYv
OpenCode SDK + CLI moved to 1.18.15 (latest stable) since the last PR
revision. Adds OPENCODE_SHA256["1.18.15"] (arm64+x64) and regenerates
the lockfile. All other in-scope bundled agents already at latest.

Gates: bun install (frozen ok), typecheck (0), bun test (418 pass),
cargo pipeline_scenarios/fixtures/streams (all green).

Claude-Session: https://claude.ai/code/session_014PWhntNeqN8yor4Bq9vKdR
Claude Code + agent-sdk moved to 2.1.226 / 0.3.226 (latest stable) since
the last PR revision. Adds CLAUDE_CODE_SHA256["2.1.226"] (arm64+x64) and
regenerates the lockfile. Lockstep verified (agent-sdk 0.3.226 carries
claudeCodeVersion 2.1.226). All other in-scope bundled agents already at
latest (codex 0.147.0, cursor 1.0.27, opencode 1.18.15, kimi 0.34.0).

Gates: bun install (frozen ok), typecheck (0), bun test (418 pass);
cargo pipeline gate pending.

Claude-Session: https://claude.ai/code/session_01JZ9iuzJ7v6ibJhrtbusRK5
Previous CI run for a9e36ec was cancelled by the concurrency group (no
superseding run followed), leaving it stuck. Branch content is unchanged
and at latest for all in-scope vendors (claude-code 2.1.226 / agent-sdk
0.3.226, codex 0.147.0, cursor 1.0.27, opencode 1.18.15, kimi 0.34.0);
frozen lockfile verified. Empty commit to trigger a fresh, uninterrupted
CI run.

Claude-Session: https://claude.ai/code/session_015s643TnSZyAeNgBMxMBqUo
Latest stable opencode-ai + @opencode-ai/sdk moved 1.18.15 -> 1.18.16.
Add OPENCODE_SHA256[1.18.16] (arm64+x64) and refresh the rolling changeset.

Claude-Session: https://claude.ai/code/session_019oPaKxonDLDS4YzurPozRu
Kimi is now behind latest stable (@moonshot-ai/kimi-code npm latest =
0.36.0). Update KIMI_VERSION and add the 0.36.0 SHA256 table (darwin +
win32, arm64 + x64), verified against the exact release download URLs.
Archive layout unchanged (single `kimi` binary at root).

Claude-Session: https://claude.ai/code/session_01Ts5JysFHQeSbD4NH3rhzHh
…kimi 0.37.2

Advance the rolling bundled-agent sweep to the newest stable upstreams:
claude-code/agent-sdk 2.1.233→2.1.235 (lockstep, claudeCodeVersion 2.1.235),
codex 0.147.0→0.148.0, kimi 0.36.1→0.37.2. Cursor 1.0.28 and OpenCode 1.18.18
already at latest. SHA256 tables extended (arm64+x64 for claude/codex; darwin+
win32 × arm64+x64 for kimi). Gates: typecheck, bun test (418), cargo pipeline
(122) all green.

Claude-Session: https://claude.ai/code/session_01YAZSKUN55iDDyiCmNfZNCb
Previous CI run (473, 048197c) was cancelled by the concurrency group with
no superseding run, leaving two required checks (Typecheck, Windows Rust
Test) stuck in a cancelled state while every completed job passed (Biome,
Clippy, Rust Test, Sidecar Test, Windows Sidecar Test, Windows Typecheck).
Branch content is unchanged and at latest for all in-scope vendors
(claude-code 2.1.235 / agent-sdk 0.3.235 lockstep, codex 0.148.0, cursor
1.0.28, opencode 1.18.18, kimi 0.37.2); frozen lockfile verified. Empty
commit to trigger a fresh, uninterrupted CI run.

Claude-Session: https://claude.ai/code/session_019gsrJ8TPYURZXDn8mvsX5p
CI's clippy toolchain (rustc 1.98) enabled chunks_exact_to_as_chunks,
which fails -D warnings on pre-existing code shared with main. Apply the
compiler-suggested as_chunks::<2>() rewrite; behavior is identical.

Claude-Session: https://claude.ai/code/session_01EzyCtLuzyFAsa3MjqVAsz2

dohooo commented Aug 22, 2026

Copy link
Copy Markdown
Owner Author

Daily bundled-agent check — 2026-08-22

No new upstream versions today. Re-checked all in-scope vendors live; every one is already pinned to its latest stable release in this PR:

Vendor latest stable (live) in this PR
claude-code / claude-agent-sdk 2.1.239 / 0.3.239
@openai/codex 0.149.0
@cursor/sdk 1.0.28
@opencode-ai/sdk + opencode-ai 1.18.21
Kimi (@moonshot-ai/kimi-code) 0.38.0

CI status (head b1d239e): all required checks green — Typecheck, Biome, Clippy, Rust Test, Sidecar Test, Windows Rust Test, Windows Sidecar Test ✓. mergeable_state = unstable (no conflict, branch up to date with main), i.e. the PR is mergeable.

One non-green check: Windows Typecheckcancelled. This is an infra flake, not a bump regression: the typecheck body itself ran clean (the non-Windows Typecheck job passed on this same commit), then the actions/cache post-step tar cache.tzst hung for ~12 min on the Windows runner and was cancelled (##[error]The operation was canceled).

I could not clear it automatically: re-running the job returns 403 Resource not accessible by integration (the automation token lacks actions: write), the branch is already up to date with main so there's no rebase to re-trigger a fresh run, and policy forbids kicking CI with an empty commit.

Needs you: either re-run the Windows Typecheck job, or merge as-is (it's a non-required check and the PR is mergeable now). I'll keep watching and verify green if it gets re-run.


Generated by Claude Code

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.

2 participants