[ca] CLI Updates: Claude Code 2.1.143 and MCP Gateway v0.3.10

[github-actions]

Summary

Version check on 2026-05-16 detected two patch-level updates: Claude Code (2.1.142 → 2.1.143) and MCP Gateway gh-aw-mcpg (v0.3.9 → v0.3.10). All other tracked CLIs and MCP servers are up to date.

Updates

Tool	Previous	New	Type
Claude Code	2.1.142	2.1.143	Patch
MCP Gateway (gh-aw-mcpg)	v0.3.9	v0.3.10	Patch

No-Change Inventory

• Copilot CLI: 1.0.48
• Codex: 0.130.0
• GitHub MCP Server: v1.0.4
• Playwright MCP: 0.0.75
• Playwright CLI: 0.1.13
• Playwright Browser: v1.60.0

Update Claude Code

• Previous: 2.1.142 → New: 2.1.143
• Risk: Low (patch release, no public changelog/repo)

View Details

Claude Code does not have a public GitHub repository, so detailed release notes are not available. Based on the version bump from 2.1.142 to 2.1.143, this is a patch-level update — typically containing bug fixes, small refinements, and minor stability improvements. No breaking changes are expected at this semver level.

Package Links:

• NPM Package: https://www.npmjs.com/package/`@anthropic-ai/claude-code`

Update MCP Gateway (gh-aw-mcpg)

• Previous: v0.3.9 → New: v0.3.10
• Released: 2026-05-15
• Risk: Low (patch release, internal refactors and one user-facing fix)

This bump touches the default sandbox.agent container image used across generated workflows. After updating DefaultMCPGatewayVersion, all 229 workflow lock files were regenerated via make build && make recompile && make recompile (double recompile is required per the constant's documented rebuild policy to refresh container SHA pins).

Key Changes

• Fix: Fall back to stderr (not stdout) when --log-dir is unwritable — fix: fall back to stderr (not stdout) when log-dir is unwritable gh-aw-mcpg#5773
• Performance: rust-guard removes hot-path scope/integrity allocations via Cow<str> and zero-alloc rank matching — rust-guard: remove hot-path scope/integrity allocations via Cow<str> and zero-alloc rank matching gh-aw-mcpg#5754
• Refactor: WASM guard detection placement and inline config validation log wrappers — Refactor WASM guard detection placement and inline config validation log wrappers gh-aw-mcpg#5774
• Docs: Reconcile docs with runtime behavior for env vars, launch flags, and config semantics — Reconcile docs with runtime behavior for env vars, launch flags, and config semantics gh-aw-mcpg#5779
• Internal: Add envutil.HasEnvVar and hasMapKeyVariants helpers in config — [Repo Assist] refactor(config): add envutil.HasEnvVar and hasMapKeyVariants helpers gh-aw-mcpg#5750
• CI: Use latest mcpg container image in smoke-copilot, add artifact readability test — feat: use latest mcpg container image in smoke-copilot gh-aw-mcpg#5705, smoke-copilot: add artifact readability test gh-aw-mcpg#5711

View Full Changelog

Bug Fixes

• fix: fall back to stderr (not stdout) when log-dir is unwritable by @Copilot — fix: fall back to stderr (not stdout) when log-dir is unwritable gh-aw-mcpg#5773

Performance

• rust-guard: remove hot-path scope/integrity allocations via Cow<str> and zero-alloc rank matching by @Copilot — rust-guard: remove hot-path scope/integrity allocations via Cow<str> and zero-alloc rank matching gh-aw-mcpg#5754

Refactors

• Refactor WASM guard detection placement and inline config validation log wrappers by @Copilot — Refactor WASM guard detection placement and inline config validation log wrappers gh-aw-mcpg#5774
• [Repo Assist] refactor(config): add envutil.HasEnvVar and hasMapKeyVariants helpers — [Repo Assist] refactor(config): add envutil.HasEnvVar and hasMapKeyVariants helpers gh-aw-mcpg#5750

Tests

• [test-improver] Improve tests for server/system_tools package — [test-improver] Improve tests for server/system_tools package gh-aw-mcpg#5715
• [test] Add tests for config.stripExtensionFieldsForValidation and assignLegacyIntAlias — [test] Add tests for config.stripExtensionFieldsForValidation and assignLegacyIntAlias gh-aw-mcpg#5762

Docs / Logging

• [log] Add debug logging to ResolveGuardPolicyOverride in guard_policy_parse.go — [log] Add debug logging to ResolveGuardPolicyOverride in guard_policy_parse.go gh-aw-mcpg#5714
• Reconcile docs with runtime behavior for env vars, launch flags, and config semantics by @Copilot — Reconcile docs with runtime behavior for env vars, launch flags, and config semantics gh-aw-mcpg#5779

CI / Smoke

• feat: use latest mcpg container image in smoke-copilot by @lpcox — feat: use latest mcpg container image in smoke-copilot gh-aw-mcpg#5705
• smoke-copilot: add artifact readability test by @lpcox — smoke-copilot: add artifact readability test gh-aw-mcpg#5711

Full comparison: github/gh-aw-mcpg@v0.3.9...v0.3.10

View Migration Guide

1. DefaultMCPGatewayVersion updated in pkg/constants/version_constants.go from v0.3.9 → v0.3.10.
2. Per the constant's documented policy, make build && make recompile && make recompile was run to refresh container SHA pins (the first recompile regenerates lock files; the second resolves the new container digest).
3. All 229 workflow .lock.yml files regenerated.
4. No API or config-shape changes for workflow authors — the --log-dir stderr fallback fix and rust-guard perf wins are transparent to consumers.

Impact Assessment

• Risk: Low
• Affects: all generated workflows that use the default sandbox.agent container (ghcr.io/github/gh-aw-mcpg:v0.3.10)
• Migration: none required for workflow authors; constant + lock files regenerated

Package Links

• Repository: https://github.com/github/gh-aw-mcpg
• Release Notes: https://github.com/github/gh-aw-mcpg/releases/tag/v0.3.10
• Compare: github/gh-aw-mcpg@v0.3.9...v0.3.10
• Docker Image: ghcr.io/github/gh-aw-mcpg:v0.3.10

Recommendations

• Merge promptly — both updates are patch-level with low risk.
• The MCPG --log-dir stderr fallback fix improves observability when the configured log directory is read-only (a real failure mode in some sandboxed runners).
• Validate the next CI run on a workflow that exercises MCPG (e.g. smoke-copilot) to confirm the new container digest resolves cleanly.

References:

• §25954711389

Generated by 🔢 CLI Version Checker · ● 7.2M · ◷

• expires on May 18, 2026, 6:19 AM UTC

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · ● 71.9K · ◷

[github-actions]

This issue is being closed as outdated. A newer issue has been created: #32968

View newer issue

---

This action was performed automatically by the CLI Version Checker workflow.