Summary
Routine CLI/dependency version check found one update: MCP Gateway (gh-aw-mcpg) v0.4.8 → v0.4.9. All other monitored CLIs/MCP servers and the eight tracked static-analysis Docker images (actionlint, syft, grype, grant, zizmor, poutine, runner-guard, yamllint) are already at their latest stable versions with unchanged digests.
MCP Gateway (gh-aw-mcpg): v0.4.8 → v0.4.9
Security
Fixes
Other changes
Full changelog (28 PRs)
Impact assessment
Risk: Low. This release is dominated by test hardening, logging, and internal refactors. The two security-relevant fixes (log secret sanitization, trusted host-path mount policy) are defensive hardening in the gateway itself and are strictly improvements for gh-aw's sandboxed MCP execution model — no action required from workflow authors. No breaking changes or removed flags were identified in the release notes.
Changes made
- Updated
DefaultMCPGatewayVersion from v0.4.8 to v0.4.9 in pkg/constants/version_constants.go.
- Ran
make fmt, then make build && make recompile && make recompile (per the doc comment on DefaultMCPGatewayVersion, which requires two recompile passes: the first regenerates lock files with the new version, the second refreshes container SHA pins).
- All 284 workflow lock files recompiled successfully (284/284 succeeded).
Known limitation: container digest not pinned
The container digest for ghcr.io/github/gh-aw-mcpg:v0.4.9 could not be resolved in this workflow's sandbox because the Docker daemon is unavailable here (Docker-in-Docker is not supported in this execution environment). As a result, the regenerated lock files reference ghcr.io/github/gh-aw-mcpg:v0.4.9 by tag only, without an @sha256:... digest pin — unlike the previous v0.4.8 entry, which had digest sha256:38bbea36cdb46a3c9d04d1db05e672966f5239b431a2022eb35881688e5721d8.
Follow-up required: re-run make recompile (twice) in an environment with Docker daemon access to resolve and pin the new digest before merging, or have CI resolve it as part of the PR checks.
Docker image check (no changes)
All eight tracked static-analysis images are at their latest stable release with matching digests — no updates needed:
| Image |
Version |
Released |
Digest match |
| actionlint |
1.7.12 |
2026-03-30 |
✓ unchanged |
| syft |
v1.50.0 |
2026-07-28 |
✓ unchanged |
| grype |
v0.116.1 |
2026-07-28 |
✓ unchanged |
| grant |
v0.6.8 |
2026-07-08 |
✓ unchanged |
| zizmor |
1.29.0 |
2026-08-01 |
✓ unchanged |
| poutine |
1.1.6 |
2026-05-22 |
✓ unchanged |
| runner-guard |
3.1.5 |
2026-04-23 |
✓ unchanged |
| yamllint |
latest |
— |
✓ unchanged |
CLI versions checked (no changes)
| Tool |
Current version |
| Claude Code |
2.1.226 |
| GitHub Copilot CLI |
1.0.78 |
| OpenAI Codex |
0.147.0 |
| GitHub MCP Server |
v1.8.0 |
| Playwright MCP |
0.0.79 |
| Playwright CLI |
0.1.18 |
| Playwright Browser |
v1.62.1 |
| Pi |
0.84.1 |
Generated by 🔢 CLI Version Checker · agent · 130.3 AIC · ⌖ 53.1 AIC · ⊞ 11.6K · ◷
Summary
Routine CLI/dependency version check found one update: MCP Gateway (gh-aw-mcpg)
v0.4.8→v0.4.9. All other monitored CLIs/MCP servers and the eight tracked static-analysis Docker images (actionlint, syft, grype, grant, zizmor, poutine, runner-guard, yamllint) are already at their latest stable versions with unchanged digests.MCP Gateway (gh-aw-mcpg): v0.4.8 → v0.4.9
DefaultMCPGatewayVersioninpkg/constants/version_constants.goSecurity
Fixes
Other changes
Full changelog (28 PRs)
Impact assessment
Risk: Low. This release is dominated by test hardening, logging, and internal refactors. The two security-relevant fixes (log secret sanitization, trusted host-path mount policy) are defensive hardening in the gateway itself and are strictly improvements for gh-aw's sandboxed MCP execution model — no action required from workflow authors. No breaking changes or removed flags were identified in the release notes.
Changes made
DefaultMCPGatewayVersionfromv0.4.8tov0.4.9inpkg/constants/version_constants.go.make fmt, thenmake build && make recompile && make recompile(per the doc comment onDefaultMCPGatewayVersion, which requires two recompile passes: the first regenerates lock files with the new version, the second refreshes container SHA pins).Known limitation: container digest not pinned
The container digest for
ghcr.io/github/gh-aw-mcpg:v0.4.9could not be resolved in this workflow's sandbox because the Docker daemon is unavailable here (Docker-in-Docker is not supported in this execution environment). As a result, the regenerated lock files referenceghcr.io/github/gh-aw-mcpg:v0.4.9by tag only, without an@sha256:...digest pin — unlike the previousv0.4.8entry, which had digestsha256:38bbea36cdb46a3c9d04d1db05e672966f5239b431a2022eb35881688e5721d8.Follow-up required: re-run
make recompile(twice) in an environment with Docker daemon access to resolve and pin the new digest before merging, or have CI resolve it as part of the PR checks.Docker image check (no changes)
All eight tracked static-analysis images are at their latest stable release with matching digests — no updates needed:
CLI versions checked (no changes)