[ca] [aw] Update agentic CLI versions and scanner image pins #67645

Overview

CLI/MCP and Docker image updates were detected for gh-aw default pins in workflow run §38115128406. I updated the local working tree constants and regenerated workflow locks with make recompile.

Updates detected

MCP Gateway remains current at v0.4.30. Threat-detect remains current at v0.5.2.

Local files updated

• pkg/constants/version_constants.go
• pkg/constants/version_constants_test.go
• pkg/cli/docker_images.go
• actions/setup/sh/install_copilot_cli.sh (regenerated default Copilot fallback)
• .github/aw/compat.json (regenerated Copilot compat max)
• .github/workflows/*.lock.yml via make recompile

Release and impact notes

GitHub Copilot CLI 1.0.90 → 1.0.95

• Timeline: 1.0.91 (2026-10-01), 1.0.92 (2026-10-05), 1.0.93 (2026-10-07), 1.0.95 (2026-10-09).
• Breaking / migration: no explicit breaking changes in v1.0.95 release notes. Prior intermediate release notes include settings-file behavior changes: user-setting keys in ~/.copilot/config.json are ignored in favor of ~/.copilot/settings.json; gh-aw should verify generated Copilot environments do not rely on the old config location.
• Features: native Microsoft Entra broker authentication on macOS with browser fallback; copilot config support for sandbox credential injectHosts keys and shell completion; --context now applies to new and resumed ACP sessions.
• Fixes: managed plugin setup retries hourly or after policy changes instead of on every message failure; earlier intermediate versions include MCP reconnect/recovery, sandbox, auth/session, context rollover, and shell streaming fixes.
• README review: README documents terminal-native agent use, GitHub integration, MCP extensibility, PAT auth using GH_TOKEN/GITHUB_TOKEN, experimental mode/autopilot, and LSP configuration via ~/.copilot/lsp-config.json or .github/lsp.json.
• CHANGELOG research: attempted a bounded changelog read from the public repository; the sandbox TLS trust store rejected the raw GitHub request with DEPTH_ZERO_SELF_SIGNED_CERT, so release notes and README were used for the detailed assessment.
• CLI help diff: cached top-level help for 1.0.93 and 1.0.95 is unchanged. copilot config --help documents settings-file behavior and supports --list, --rm, --json, --repo, and --local; copilot environment --help remains unavailable as a direct subcommand.
• Impact: medium. Auth and sandbox credential changes are relevant to gh-aw's Copilot runtime; verify PAT and MCP scenarios after merge.
• Links: https://github.com/github/copilot-cli/releases/tag/v1.0.95

OpenAI Codex 0.159.3 → 0.162.1

• Timeline: 0.160.0 (2026-10-01), 0.160.1 (2026-10-05), 0.161.0 (2026-10-07), 0.162.1 (2026-10-09).
• Breaking / migration: none identified in the release summary, but this spans multiple releases with daemon, TUI, MCP, sandbox, and auth changes.
• Fixes in 0.162.1: TUI crash when asynchronous questions contain multiple lines; startup failures caused by differences between a running background server's feature settings and CLI defaults. Compatibility checks now apply only to explicit command-line feature overrides.
• Earlier intermediate features/fixes: older task browsing, projectless sessions, Guardian context retrieval, model catalog and fork/cloud/session enhancements; Windows sandbox and PowerShell fallback repairs; SQLite stall/corruption handling; MCP OAuth/token exchange/storage updates; retry and exec-server recovery.
• CLI help diff: cached 0.162.1 help includes doctor, sandbox, migrate-rollouts, cloud, exec-server, and features; no top-level help regression observed against the cached prior output.
• Impact: medium. Startup compatibility and daemon behavior are directly relevant to long-running or resumed gh-aw Codex runs.
• Links: https://github.com/openai/codex/releases/tag/rust-v0.162.1
• External PR references: Preserve line breaks and links in multiline async questions openai/codex#51866, Limit daemon feature compatibility checks to explicit CLI overrides openai/codex#52648

GitHub MCP Server v1.12.2 → v2.0.2

• v2.0.2 release notes: restore typed tool HTTP header validation.
• v2.0.1 intermediate note from prior check: publish proper module path for Go library users.
• Breaking / migration: medium risk because this crosses a major version boundary from v1.12.2 to v2.x. Validate GitHub MCP tool schemas and behavior in workflow runs.
• Impact: medium for gh-aw because GitHub MCP is a core read/tooling path.
• Release: https://github.com/github/github-mcp-server/releases/tag/v2.0.2
• External PR reference: fix(inventory): restore typed tool HTTP header validation github-mcp-server#3454

Playwright CLI 0.1.21 → 0.1.22

• Release date: 2026-09-28; outside the 72-hour npm cooldown. Test metadata was updated to 2026-09-28T23:24:31.286Z from npm.
• Fixes: run-code supports timers, fetch, URL, Buffer, crypto, AbortController, and text encoders while keeping require and process unavailable; find --filename=results.md; dialog reporting for navigation; browser-close during download no longer crashes; install-browser --no-shell; webmcp-call stale tab/frame and Chromium 155+ fixes; snapshots quote regex-like names; bundled skill only preapproves Playwright commands rather than any npm/npx.
• CLI help: cached top-level help confirms no removed core commands.
• Impact: low and security-positive because command preapproval is narrower.
• Release: https://github.com/microsoft/playwright-cli/releases/tag/v0.1.22

Pi 1.0.0 → 1.1.0

• Source: npm metadata and cached CLI help comparison; no public GitHub release notes were available.
• NPM metadata: Node engine now requires >=22.19.0; package has SLSA provenance attestations.
• CLI help: --tools documents that only +name/-name entries add to or remove from defaults, and keeps MCP tools unless an entry starts with mcp__.
• Impact: medium because this is a minor-version bump and it changes documented tool-selection semantics.

Claude Code 2.1.288 → 2.1.296

• Source: npm metadata and cached CLI help comparison; no public GitHub repository/release notes.
• NPM metadata: Node engine remains >=22.0.0; package bin remains claude.
• CLI help diff: cached top-level help for 2.1.293 and 2.1.296 begins identically; no obvious top-level option changes observed.
• Impact: low.

Docker image audit

Docker image digests were resolved for every configured scanner image. Syft and Grype version updates are now outside the 3-day cooldown and were applied. All other pinned scanner digests were unchanged; YamllintImage still uses latest and its current digest is unchanged.

Other resolved scanner digests:

Syft v1.54.1 notes

• Fixes: deterministic packages.lock dependency resolution; local Podman image attestation output fix.
• Dependencies: 9 updated packages, including go-rpmdb, stereoscope, Docker CLI, SQLite, compression, sigstore, and SIF dependencies.
• Release: https://github.com/anchore/syft/releases/tag/v1.54.1
• External PR references: fix(dotnet): resolve packages.lock dependencies deterministically  anchore/syft#5210, Add container-storage support for Podman and Buildah anchore/syft#5368

Grype v0.120.1 notes

• Fixes: Windows unit-test handle leaks; table presenter spurious , ... in FIX column when all fix versions are already shown.
• Dependencies: 9 updated packages, including Syft v1.54.1, Docker CLI, sigstore, and SIF dependencies.
• Release: https://github.com/anchore/grype/releases/tag/v0.120.1
• External PR references: ci: run unit tests on windows and fix the handle leaks it surfaced anchore/grype#3766, fix(table): only hint at more fix versions when one was omitted anchore/grype#3770

Validation

• go fmt ./pkg/constants ./pkg/cli passed.
• make recompile passed in the foreground: 337/337 workflows compiled; existing repository warnings only.
• go test ./pkg/constants ./pkg/cli -run 'TestDefaultCLIMCPVersions|TestDefaultPlaywrightCLIVersionOutsideCooldownWindow|TestDefaultThreatDetectReleasePins' -short passed.
• make fmt was attempted. The Go formatting phase passed, but the JavaScript dependency install path needed by Prettier could not complete because npm ci failed on a TLS trust-store error while fetching codeload.github.com (DEPTH_ZERO_SELF_SIGNED_CERT). I did not disable TLS verification.

Next actions

1. Review and merge the constants, scanner image pins, and generated lock changes.
2. Pay special attention to Copilot CLI settings-file behavior and GitHub MCP Server v2 compatibility.
3. Re-run the full make fmt/make agent-report-progress path in an environment with a working Node/GitHub TLS trust store.

References:

• §38115128406

Generated by 🔢 CLI Version Checker · pi · gpt55 · 291.9 AIC · ⌖ 20.2 AIC · ⊞ 11.2K · ◷

• expires on Oct 12, 2026, 9:45 PM UTC-08:00