Skip to content

chore: refresh stable Claude runtime pin to 2.1.300 #177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
makeitfutureDev merged 1 commit into from
Oct 15, 2026
Merged

chore: refresh stable Claude runtime pin to 2.1.300 #177

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ product overview.

## Unreleased

- Refresh the channel runtime engine pins to Claude Code 2.1.299 and Codex CLI 0.162.1.
- Refresh the channel runtime engine pins to Claude Code 2.1.300 and Codex CLI 0.162.1.

## 0.6.3 — 2026-10-11

Expand Down
2 changes: 1 addition & 1 deletion containers/versions.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
"comment": "Pinned toolchain for the channel image. Keep `claude` and `codex` at the versions the gateway host runs, so a channel behaves identically on either runtime backend; bump deliberately, rebuild, and let the image-id fingerprint recreate the containers. `imageSpecVersion` is the image CONTRACT (paths, PATH, baked-in packages), not the pins: bump it when the image gains or moves something the daemon relies on, keep it equal to IMAGE_SPEC_VERSION in src/runtimes/container/image-paths.js (a test pins them together), and the daemon will tell an operator at boot when the built image is older.",
"base": "node:22-bookworm-slim",
"npm": {
"@anthropic-ai/claude-code": "2.1.299",
"@anthropic-ai/claude-code": "2.1.300",
"@openai/codex": "0.162.1",
"mcp-remote": "0.14.3",
"vercel": "59.11.1",
Expand Down
2 changes: 1 addition & 1 deletion docs/COMPATIBILITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ definitions are in `TEST-PLAN.md` and `docs/RELEASE-ACCEPTANCE.md`.
| --- | --- | --- |
| Operating system | Linux (systemd) with rootless Podman; Ubuntu 24.04 tested | CI on Ubuntu |
| Node.js | 22.13 minimum; 24 LTS. SQLite FTS5 (channel-memory search index) is present from the later 22.x builds and 24; on a build without it the daemon boots and memory search uses a plain scan | Full matrix CI |
| Claude Code | Pinned nightly target `2.1.299` (official installer) | Real CLI surface + stub transport |
| Claude Code | Pinned nightly target `2.1.300` (official installer) | Real CLI surface + stub transport |
| Codex CLI | Pinned nightly target `0.162.1`. The container login relay relies on three behaviors verified on 0.156.1 (2026-09-26 spike, `TEST-PLAN.md` P4): a turn runs on an `auth.json` with an access token and an empty refresh token; a valid access token is not refreshed because of `last_refresh` age; `login status` and a turn accept a JWT whose signature segment is a placeholder. `codex exec` needs a closed stdin. Re-run the spike on a Codex bump | Real CLI surface + stub transport; the relay spike before promotion |
| SQLite | Built-in `node:sqlite` | Migrations + backup/restore quick-check |
| VS Code (editor attach) | Any client. Servers for `1.139.0` and `1.138.0` are shared in the channel image (image spec 1.5.0); another version downloads its own into the channel volume as before | Live image test (`npm run test:live-container`) + a real Remote-SSH / attach connection before promotion |
Expand Down
Loading