-
Notifications
You must be signed in to change notification settings - Fork 122
Description
Two CLI version updates are available for gh-aw agentic workflow dependencies.
Summary
- Playwright Browser: v1.58.1 → v1.58.2 (patch release with bug fixes)
- MCP Gateway: v0.0.103 → v0.0.109 (6 patch versions with new features and critical fixes)
Update Priority
Playwright Browser: Low - Minor bug fixes
MCP Gateway: High - Critical payload handling fixes and new configurability
Playwright Browser Update
Version Information
- Current Version: v1.58.1
- Latest Version: v1.58.2
- Release Date: 2026-02-06
- Update Type: Patch release
Breaking Changes
None
Key Features
Minor bug fixes for trace viewer and Chromium on macOS
View Full Changelog
Release Highlights (from GitHub)
Bug Fixes:
- #39121 fix(trace viewer): make paths via stdin work
- #39129 fix: do not force swiftshader on chromium mac
Browser Versions:
- Chromium 145.0.7632.6
- Mozilla Firefox 146.0.1
- WebKit 26.0
Impact Assessment
- Risk: Low
- Affects: Playwright browser automation in workflows using the
@playwright/mcptool - Migration Notes: Drop-in replacement, no configuration changes required
Recommendations
- Update Priority: Low - Can be bundled with next maintenance update
- Testing: Standard workflow tests should be sufficient
- Rollout: Safe to deploy immediately
Package Links
- Repository: https://github.com/microsoft/playwright
- Release Notes: https://github.com/microsoft/playwright/releases
- Specific Release: https://github.com/microsoft/playwright/releases/tag/v1.58.2
- Docker Image:
mcr.microsoft.com/playwright:v1.58.2
MCP Gateway Update
Version Information
- Current Version: v0.0.103
- Latest Version: v0.0.109
- Intermediate Versions: v0.0.104, v0.0.105, v0.0.106, v0.0.107, v0.0.108
- Release Timeline:
- v0.0.104: 2026-02-06
- v0.0.105: 2026-02-06
- v0.0.107: 2026-02-06
- v0.0.109: 2026-02-06 (latest)
- Update Type: Six patch releases in rapid succession
Breaking Changes
None - all changes are backward compatible
Key Features
v0.0.109 - Configurable Payload Size Threshold:
- New CLI flag
--payload-size-thresholdto control when tool responses are stored to disk vs. returned inline - Environment variable
MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLDfor configuration - Config file option
payload_size_threshold - Default threshold: 1024 bytes
- Priority: CLI flag > Environment variable > Config file > Default
- Impact: Allows tuning memory usage and performance based on workload
v0.0.107 - Critical Payload Handling Fixes:
- Fixed large payload metadata not reaching clients (#773, #766)
- Fixed payload file permissions - now world-readable (0755 for directories, 0644 for files)
- Payload metadata (queryID, payloadPath, schema, preview) now properly included in
CallToolResult.Content - Agents can now access full payloads from mounted directories
v0.0.105 - Large Payload Testing & Enhanced Logging:
- Comprehensive agentic workflow to validate large payload storage (#730)
- Enhanced payload middleware logging with size info in multiple units
- Tests verify MCP Gateway stores large responses to
/tmp/jq-payloads/{sessionID}/{queryID}/payload.json - Validates agents can access payloads through volume mounts at
/workspace/mcp-payloads/
View Full Changelog
v0.0.104
Large Payload Testing Infrastructure:
- #730 Add agentic workflow to test large payload storage and agent access
- #731 Fix MCP Gateway mount propagation in large-payload-tester workflow
- #733 Fix large payload tester mount isolation - remove test data from gateway
- #735 Fix large-payload-tester: add missing test data mount to MCP gateway
- #764 Fix large-payload-tester agent prompt numbering and grammar
Payload Middleware Improvements:
- #766 Fix large payload middleware: populate CallToolResult.Content field and add extensive logging
GitHub Agentic Workflows Updates:
v0.0.105
Same as v0.0.104 with enhanced release notes and documentation
v0.0.106
Infrastructure Updates:
Middleware Refactoring:
- #771 refactor(middleware): define PayloadMetadata as struct with constant for type safety
- #773 fix(middleware): use world-readable permissions for payload files
v0.0.107
Same as v0.0.106 with enhanced release notes documenting the critical fixes
v0.0.108
Internal Improvements:
- #714 [test-improver] Improve tests for auth package
- #751 [log] Add debug logging to DIFC agent module
New Feature:
- #790 Add configurable payload size threshold for inline vs disk storage
v0.0.109
Configurable Payload Threshold (#790):
- Control when tool response payloads are stored to disk vs. returned inline
- Configure via
--payload-size-thresholdCLI flag,MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLDenv var, or config file - Default: 1024 bytes
- Smaller thresholds reduce memory pressure for high-volume agents
- Larger thresholds minimize disk I/O for moderate payload agents
Internal Improvements:
View Migration Guide
Updating from v0.0.103 to v0.0.109
Step 1: Update constants.go
The version constant has been updated in pkg/constants/constants.go:
const DefaultMCPGatewayVersion Version = "v0.0.109"Step 2: Recompile workflows
Run make recompile to update workflow lock files with the new MCP Gateway version:
make recompileThis will update all .github/workflows/*.lock.yml files to reference ghcr.io/github/gh-aw-mcpg:v0.0.109.
Step 3: Test large payload workflows
If your workflows use MCP Gateway's large payload feature (responses >1KB by default):
- Verify payload files are accessible to agents
- Check that volume mounts are correctly configured
- Confirm payload metadata is present in tool responses
Step 4: Optional - Tune payload threshold
If you want to customize the payload size threshold:
Via environment variable (in workflow frontmatter):
sandbox:
agent:
env:
MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLD: "2048" # 2KB thresholdVia CLI flag (if launching manually):
gh-aw-mcpg --payload-size-threshold 2048Via config file (if using configuration files):
{
"payload_size_threshold": 2048
}Breaking Changes
None - all updates are backward compatible
Known Issues
None reported
Impact Assessment
- Risk: Medium - Critical fixes for payload handling, but well-tested
- Affects: All workflows using MCP Gateway (feature flag:
mcp-gateway) - Migration Notes: Drop-in replacement, optional threshold tuning available
Recommendations
- Update Priority: High - Critical fixes for large payload handling
- Testing Strategy:
- Test workflows with large MCP tool responses (>1KB)
- Verify payload files are accessible from agent containers
- Validate payload metadata in tool responses
- Rollout Plan: Deploy with next maintenance update, monitor payload handling
Package Links
- Repository: https://github.com/github/gh-aw-mcpg
- Release Notes: https://github.com/github/gh-aw-mcpg/releases
- Latest Release: https://github.com/github/gh-aw-mcpg/releases/tag/v0.0.109
- Docker Image:
ghcr.io/github/gh-aw-mcpg:v0.0.109
Changes Made
The following files have been updated:
- ✅
pkg/constants/constants.go- UpdatedDefaultPlaywrightBrowserVersiontov1.58.2 - ✅
pkg/constants/constants.go- UpdatedDefaultMCPGatewayVersiontov0.0.109 ⚠️ Workflow lock files (.github/workflows/*.lock.yml) - Need recompilation viamake recompile
Next Steps
- Review this issue and approve the updates
- Run
make recompilelocally to regenerate workflow lock files - Create a PR with the changes
- Merge after CI passes
- Monitor workflows for any payload handling issues (especially for MCP Gateway update)
Additional Context
Workflow Run: §21779965257
Cache Information: Version check results saved to /tmp/gh-aw/cache-memory/version-check-last-run.json
Previous Update: §21750432848 - Updated Claude Code, Copilot, Codex, and Playwright MCP
AI generated by CLI Version Checker
- expires on Feb 9, 2026, 12:22 PM UTC