You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
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.
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:
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-json failed with an EACCES error on the sandbox's .awf-home go mod cache, a known sandbox-only issue unrelated to these edits.
make recompile run twice in the foreground — 294/294 workflows compiled successfully both passes.
Confirmed ghcr.io/github/gh-aw-mcpg and ghcr.io/github/github-mcp-server are emitted as tag-only references (no @sha256 pin) in generated lock files by design — this differs from the gh-aw-firewall images, which the compiler pins to an explicit digest via download_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 status shows 296 modified .lock.yml files plus pkg/constants/version_constants.go — as expected for a version bump across all generated workflows. Per this task's instructions, .lock.yml files 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 · ◷
Summary
Automated CLI/MCP version check found 4 updates. Local edits applied to
pkg/constants/version_constants.go,make fmtandmake 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 recompileto actually updatepkg/constants/version_constants.goand the 294 generated.lock.ymlfiles.Claude Code CLI: 2.1.245 → 2.1.247
OpenAI Codex CLI: 0.149.1 → 0.150.1
rust-v0.150.0 highlights
New Features
@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)/renamesuggests an editable title (Generate descriptive TUI thread titles openai/codex#40492, Suggest conversation-based thread titles in/renameopenai/codex#40495).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)Interrupthooks for active top-level turn interruption (Add hooks for interrupted turns openai/codex#40511)Bug Fixes
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)Full changelog: openai/codex@rust-v0.149.0...rust-v0.150.0
rust-v0.150.1
Bug Fixes
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.mduntrusted-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
Release notes
Highlights
What's Changed
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#3155Full 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 thatget_mealready 403s under the integration token.MCP Gateway (gh-aw-mcpg): v0.4.10 → v0.4.12
v0.4.11 → v0.4.12 changes
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#11912proxy.enclaveToolAndArgs— [test-improver] Improve tests for enclavegithub Policy coverage gh-aw-mcpg#11881, [test] Add tests for proxy.enclaveToolAndArgs gh-aw-mcpg#11928Full 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:rhysd/actionlint:1.7.12@sha256:b1934ee5f1c509618f2508e6eb47ee0d3520686341fec936f3b79331f9315667anchore/syft:v1.51.0@sha256:678bfa565b60f747aac0f8e964fe5588a24445b8d0a480e91f6efd70020dfbb0anchore/grype:v0.117.0@sha256:ddf9e9f204049f3a4a0955ef70873cabab6a31432125ad4f20a490b54950a253anchore/grant:v0.6.8@sha256:172463611795f43b77302cdfbd7b3f81295492a7330e0820cfe41c3674920237ghcr.io/zizmorcore/zizmor:1.29.0@sha256:863026d54f91271b10b60b67ad8054cb37120167e162482597db102b3026a284ghcr.io/boostsecurityio/poutine:1.1.6@sha256:722a8e0999b583c1540fe2974e691032b2d9d21b9256a17965132b6bfd0081b0ghcr.io/vigilant-llc/runner-guard:3.1.5@sha256:2df426ef96d21f1622e05b21329f26bd263fc46110609cefb6afe43457613ac0pipelinecomponents/yamllint:latest@sha256:5ab5eb7da0ed5e606b07c1723fc8b275e925189f70ac259b26b7329cb5f8f44dUnchanged 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.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.