Repository navigation
[ca] CLI/MCP version updates: Claude Code 2.1.247, Codex 0.150.1, GitHub MCP Server v1.11.0, MCP Gateway v0.4.12 #56296
Description
Summary
Automated CLI/MCP version check found 4 updates. Local edits applied to pkg/constants/version_constants.go, make fmt and make recompile (x2) run successfully (294/294 workflows compiled both passes). Docker images used by static-analysis steps (Actionlint, Syft, Grype, Grant, Zizmor, Poutine, RunnerGuard, Yamllint) were also checked — no version or digest changes.
Note: this workflow only files an issue; it does not open a PR. A maintainer (or a follow-up automation) needs to apply these same constant edits and run make fmt && make recompile && make recompile to actually update pkg/constants/version_constants.go and the 294 generated .lock.yml files.
Claude Code CLI: 2.1.245 → 2.1.247
- Package: https://www.npmjs.com/package/``@anthropic-ai/claude-code``
- No public GitHub repository; release notes unavailable, only NPM publish timestamps (2.1.246 published 2026-08-25, 2.1.247 published 2026-08-26).
- Risk: Low — patch-level bump, no breaking changes surfaced in NPM metadata.
OpenAI Codex CLI: 0.149.1 → 0.150.1
- Repository: https://github.com/openai/codex
- Two intermediate releases: rust-v0.150.0 (2026-08-26) and rust-v0.150.1 (2026-08-27).
rust-v0.150.0 highlights
New Features
- Reference other Codex tasks with
@mentions; read, create, or message tasks from the terminal (Add TUI tools for managing Codex tasks openai/codex#40308, Add task mentions to the TUI composer openai/codex#40315) /copynow offers a picker for full responses, individual code blocks, and blockquotes (Add a response target picker to/copyopenai/codex#39997)- Unnamed terminal tasks get descriptive titles automatically;
/renamesuggests an editable title (Generate descriptive TUI thread titles openai/codex#40492, Suggest conversation-based thread titles in/renameopenai/codex#40495) - Markdown links appear as clickable labels in supported terminals (Render Markdown links as clickable labels in supported terminals openai/codex#40471)
- Shortcuts to cycle permission modes;
.repeats last edit in Vim mode (Add keybindings for cycling TUI permission modes openai/codex#39873, Add dot-repeat to Vim mode openai/codex#40521) - New
Interrupthooks for active top-level turn interruption (Add hooks for interrupted turns openai/codex#40511)
Bug Fixes
- Untrusted projects no longer read project-level
AGENTS.md; managed deny-read rules stay enforced after permission changes (Ignore project instructions for untrusted projects openai/codex#39837, Preserve managed deny-read rules across permission updates openai/codex#40004) - Improved credential redaction in app-server diagnostics (Keep credentials out of app-server logs openai/codex#39993)
- Fixed remote MCP bearer-token lookup and required-server startup (Resolve HTTP MCP bearer tokens in executor environments openai/codex#39926, Honor required MCP servers from selected executors openai/codex#39952, Preserve MCP compatibility with older executors openai/codex#39979)
- Fixed elevated Windows sandbox setup under Unicode user paths (Fix elevated Windows sandbox setup activation openai/codex#39971, Preserve Unicode paths in Windows batch aliases openai/codex#40570)
- Prevented Unix shutdown hangs from detached processes (Prevent Unix PTY I/O from blocking runtime shutdown openai/codex#40460)
- Fixed conversation compaction/multi-agent compatibility for Amazon Bedrock models (Use multi-agent V1 for Amazon Bedrock models openai/codex#39804, Use Responses compaction for Amazon Bedrock openai/codex#39825)
Full changelog: openai/codex@rust-v0.149.0...rust-v0.150.0
rust-v0.150.1
Bug Fixes
- Remote compaction now counts retained images toward its token budget by default, trimming older images as needed (Backport retained-image compaction budgeting to 0.150 openai/codex#41003)
Full changelog: openai/codex@rust-v0.150.0...rust-v0.150.1
Risk: Low — no breaking changes; mostly TUI/UX features and targeted fixes. The AGENTS.md untrusted-project change and MCP bearer-token fixes are worth a quick look since gh-aw workflows configure MCP servers and rely on Codex reading repo instructions.
GitHub MCP Server: v1.10.1 → v1.11.0
- Repository: https://github.com/github/github-mcp-server
- Released: 2026-08-25
Release notes
Highlights
- Smarter OAuth challenges: per-call scope checks request only the permissions each tool invocation needs, with runtime checks where required.
- Improved browser OAuth support: CORS now works across OAuth discovery routes, with configurable authorization-server URLs.
- Improved sub-issue workflow: create parent and sub-issues atomically.
- Better HTTP caching for STDIO: REST responses support ETag conditional requests.
- Runtime refresh: upgraded to Go 1.27, plus routine security and dependency updates.
What's Changed
- feat(http): add --authorization-server flag to override OAuth AS URL — feat(http): add --authorization-server flag to override OAuth AS URL github-mcp-server#2900
- Name the root command after the installed binary — Name the root command after the installed binary github-mcp-server#2998
- fix(http): preserve CORS across OAuth routes — fix(http): preserve CORS across OAuth routes github-mcp-server#3147
- Add atomic parent issue creation — Add atomic parent issue creation github-mcp-server#3134
- Add ETag conditional requests to the REST transport — Add ETag conditional requests to the REST transport github-mcp-server#3026
- Add per-call OAuth scope checks — Add per-call OAuth scope checks github-mcp-server#3128
- Dependency bumps: codeql-action, docker/setup-buildx-action, go-chi/chi, distroless/base-debian12, golang 1.25.13→1.27.0-alpine, testify — build(deps): bump github/codeql-action from 4 to 4.37.4 github-mcp-server#3004, build(deps): bump docker/setup-buildx-action from 4.2.0 to 4.3.0 github-mcp-server#3157, build(deps): bump github.com/go-chi/chi/v5 from 5.3.1 to 5.3.2 github-mcp-server#3156, build(deps): bump distroless/base-debian12 from
76b3162tofabbf1cgithub-mcp-server#3154, build(deps): bump golang from 1.25.13-alpine to 1.27.0-alpine github-mcp-server#3153, build(deps): bump github.com/stretchr/testify from 1.12.0 to 1.12.1 github-mcp-server#3155
Full changelog: github/github-mcp-server@v1.10.1...v1.11.0
Risk: Low/Medium — per-call OAuth scope checks and CORS/authorization-server changes only affect the HTTP/OAuth transport; gh-aw's usage is via the Docker image with the read-only GitHub MCP server (STDIO/manifest driven), so impact should be limited, but worth confirming get_me / other tool listings still resolve correctly after the bump given this workflow's own note that get_me already 403s under the integration token.
MCP Gateway (gh-aw-mcpg): v0.4.10 → v0.4.12
- Repository: https://github.com/github/gh-aw-mcpg
- Two intermediate releases: v0.4.11 (2026-08-26) and v0.4.12 (2026-08-26)
v0.4.11 → v0.4.12 changes
- Add explicit DNS SANs to proxy TLS certificates — Add explicit DNS SANs to proxy TLS certificates gh-aw-mcpg#11933
- Centralize visibility literals in
private_flag_from_repo_object(rust-guard refactor) — [Repo Assist] refactor(rust-guard): centralize visibility literals in private_flag_from_repo_object gh-aw-mcpg#11912 - Add debug logging to enclavegithub policy parsing/validation — [log] Add debug logging to enclavegithub policy parsing and validation gh-aw-mcpg#11880
- Test coverage improvements for enclavegithub policy and
proxy.enclaveToolAndArgs— [test-improver] Improve tests for enclavegithub Policy coverage gh-aw-mcpg#11881, [test] Add tests for proxy.enclaveToolAndArgs gh-aw-mcpg#11928 - v0.4.11 itself was a large batch of internal test/logging/refactor PRs (rust-guard consolidation, OpenTelemetry endpoint validation, capability-bound enclave issue reads, etc.) with no user-facing behavior changes called out.
Full changelog: github/gh-aw-mcpg@v0.4.10...v0.4.12
Risk: Low — mostly internal test/logging/refactor work; the added DNS SANs for proxy TLS certs is a hardening change relevant to gh-aw's MCP Gateway sandbox topology. No API/config schema changes noted.
Docker images (static analysis) — no changes
Checked digests directly against registries for all 8 images pinned in pkg/cli/docker_images.go; every version and digest matched the current pin exactly, so no edits were needed:
- ActionlintImage —
rhysd/actionlint:1.7.12@sha256:b1934ee5f1c509618f2508e6eb47ee0d3520686341fec936f3b79331f9315667 - SyftImage —
anchore/syft:v1.51.0@sha256:678bfa565b60f747aac0f8e964fe5588a24445b8d0a480e91f6efd70020dfbb0 - GrypeImage —
anchore/grype:v0.117.0@sha256:ddf9e9f204049f3a4a0955ef70873cabab6a31432125ad4f20a490b54950a253 - GrantImage —
anchore/grant:v0.6.8@sha256:172463611795f43b77302cdfbd7b3f81295492a7330e0820cfe41c3674920237 - ZizmorImage —
ghcr.io/zizmorcore/zizmor:1.29.0@sha256:863026d54f91271b10b60b67ad8054cb37120167e162482597db102b3026a284 - PoutineImage —
ghcr.io/boostsecurityio/poutine:1.1.6@sha256:722a8e0999b583c1540fe2974e691032b2d9d21b9256a17965132b6bfd0081b0 - RunnerGuardImage —
ghcr.io/vigilant-llc/runner-guard:3.1.5@sha256:2df426ef96d21f1622e05b21329f26bd263fc46110609cefb6afe43457613ac0 - YamllintImage —
pipelinecomponents/yamllint:latest@sha256:5ab5eb7da0ed5e606b07c1723fc8b275e925189f70ac259b26b7329cb5f8f44d
Unchanged CLIs/MCP servers
Copilot CLI (1.0.80), Playwright MCP (0.0.79), Playwright CLI (0.1.18), Playwright Browser (v1.62.1), Pi (0.84.3), threat-detect (v0.4.12) all matched their pinned versions — no action needed.
Verification performed
make fmt— Go and JS formatting succeeded;fmt-jsonfailed with an EACCES error on the sandbox's.awf-homego mod cache, a known sandbox-only issue unrelated to these edits.make recompilerun twice in the foreground — 294/294 workflows compiled successfully both passes.- Confirmed
ghcr.io/github/gh-aw-mcpgandghcr.io/github/github-mcp-serverare emitted as tag-only references (no@sha256pin) in generated lock files by design — this differs from thegh-aw-firewallimages, which the compiler pins to an explicit digest viadownload_docker_images.sh. Manually verified ghcr.io registry access itself works from the sandbox and resolved the mcpg v0.4.12 digest (sha256:92d5377b6bd32cd5b9306b2a553f7ef3549bccff9207e46f931e7249bc718713) independently, confirming the missing pin is expected compiler behavior rather than a network/auth failure. git statusshows 296 modified.lock.ymlfiles pluspkg/constants/version_constants.go— as expected for a version bump across all generated workflows. Per this task's instructions,.lock.ymlfiles are not committed here; a maintainer needs to reapply the constant edits and recompile to produce a mergeable diff.
Generated by 🔢 CLI Version Checker · claude · agent · 108.4 AIC · ⌖ 8.61 AIC · ⊞ 12.8K · ◷
- expires on Aug 29, 2026, 12:15 AM UTC-08:00
Activity