[ca] Update MCP Gateway to v0.2.4

[github-actions]

Summary

MCP Gateway (gh-aw-mcpg) has a new release. pkg/constants/constants.go has been updated and workflows recompiled (177/177).

• Version: v0.2.3 → v0.2.4
• Released: 2026-03-24 (today)
• Docker Image: ghcr.io/github/gh-aw-mcpg:v0.2.4

Key Changes

• Proxy + github-script smoke tests — End-to-end tests now validate the proxy integration with github-script, catching regressions in real-world workflow scenarios. Workflows recompiled for gh-aw v0.63.0. (feat: add proxy+github-script smoke test, recompile workflows for gh-aw v0.63.0 gh-aw-mcpg#2412)
• Proxy response envelope fix — Corrected malformed response envelopes in proxy mode, ensuring downstream github-script consumers receive well-structured JSON-RPC responses. (fix: proxy response envelopes + smoke test for github-script integration gh-aw-mcpg#2420)

Impact Assessment

• Risk: Low
• Affects: Sandbox agent container (default sandbox.agent container), proxy mode with github-script integrations
• Breaking Changes: None

Version Check Summary (2026-03-24)

Tool	Current	Latest	Status
Claude Code	latest	2.1.81	✅ (uses latest)
Copilot CLI	latest	1.0.11	✅ (uses latest)
Codex	latest	0.116.0	✅ (uses latest)
GitHub MCP Server	v0.32.0	v0.32.0	✅
MCP Gateway	v0.2.3	v0.2.4	🔄 Updated
APM	v0.8.4	v0.8.4	✅
Playwright MCP	0.0.68	0.0.68	✅
Playwright Browser	v1.58.2	v1.58.2	✅

Package Links

• Repository: https://github.com/github/gh-aw-mcpg
• Release Notes: https://github.com/github/gh-aw-mcpg/releases/tag/v0.2.4
• Full Changelog: github/gh-aw-mcpg@v0.2.3...v0.2.4

References:

• §23475935999

Generated by CLI Version Checker · ◷

• expires on Mar 26, 2026, 6:20 AM UTC

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

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

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 · ◷

[github-actions]

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

View newer issue

---

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