Skip to content

[ca] Update CLI versions: Claude Code 2.1.7, Copilot 0.0.382, Codex 0.81.0, MCP Gateway v0.0.59 #9989

@github-actions

Description

@github-actions

CLI Version Updates - January 14, 2026

This issue tracks updates for 4 agentic CLI tools that have new versions available.

Summary

  • Claude Code: 2.1.6 → 2.1.7
  • Copilot CLI: 0.0.381 → 0.0.382
  • Codex: 0.80.0 → 0.81.0
  • MCP Gateway: v0.0.56 → v0.0.59

Files Modified: pkg/constants/constants.go has been updated with the new versions.

Action Required: Run make recompile to regenerate workflow files from constants.


1. Update Claude Code (2.1.6 → 2.1.7)

Version: 2.1.6 → 2.1.7
Release Date: January 14, 2026 (published at 00:00:19 UTC)
Timeline: Same-day update

Changes

  • Breaking Changes: None
  • New Features: No public changelog available for this version
  • Bug Fixes: No public changelog available
  • Security: None reported
  • CLI Discovery: Cannot verify without installing (read-only filesystem)

Impact Assessment

  • Risk: Low
  • Affected Features: None identified
  • Migration Required: No

Package Links


2. Update Copilot CLI (0.0.381 → 0.0.382)

Version: 0.0.381 → 0.0.382
Release Date: January 14, 2026 (published at 18:55:01 UTC)
Timeline: Same-day update

Changes

  • Breaking Changes: None identified
  • New Features: Unknown (no public release notes)
  • Bug Fixes: Unknown (no public release notes)
  • Security: None reported
  • CLI Discovery: Cannot verify without installing

Impact Assessment

  • Risk: Low to Medium (requires integration testing per WARNING in constants.go)
  • Affected Features: All Copilot-based workflows
  • Migration Required: No, but full integration test recommended

Package Links

Notes

  • WARNING: Per constants.go line 246, "UPGRADING COPILOT CLI REQUIRES A FULL INTEGRATION TEST RUN TO ENSURE COMPATIBILITY"
  • Unable to access detailed changelog as repository may be private

3. Update Codex (0.80.0 → 0.81.0)

Version: 0.80.0 → 0.81.0
Release Date: January 14, 2026 (published at 18:12:36 UTC)
Timeline: Same-day update

Changes

Breaking Changes

New Features

Bug Fixes

Documentation

Chores

Impact Assessment

  • Risk: Medium (default model change could affect API behavior)
  • Affected Features:
    • All Codex API calls (new default model)
    • Headless environments (improved login flow)
    • Linux sandbox configurations (new read-only mount capability)
    • Windows sandbox workflows (improved safety prompts)
  • Migration Required: No code changes required, but test with new default model

Package Links


4. Update MCP Gateway (v0.0.56 → v0.0.59)

Versions: v0.0.56 → v0.0.57 → v0.0.58 → v0.0.59
Release Dates:

  • v0.0.57: January 14, 2026 (00:23:03 UTC)
  • v0.0.58: January 14, 2026 (00:28:32 UTC)
  • v0.0.59: January 14, 2026 (14:06:19 UTC)
    Timeline: Three releases in 14 hours

Changes in v0.0.57-v0.0.58

New Features

Improvements

Changes in v0.0.59

⚠️ Breaking Changes

Mount Path Validation Now Enforces Absolute Paths

Per MCP specification v1.7.0 §4.1.5, all mount paths (both host and container) must be absolute. Configurations with relative paths like "data:/app:ro" or "./config:/app/config:ro" will be rejected.

Action Required: Review config.toml or config.json files and update any relative mount paths to absolute paths starting with /.

Example:

// ❌ Will now fail
"mounts": ["data:/app/data:ro", "./config:/app/config:ro"]

// ✅ Correct format
"mounts": ["/var/app/data:/app/data:ro", "/home/user/config:/app/config:ro"]

Why this matters: Absolute paths enforce security and portability guarantees required by the MCP specification, preventing ambiguous path resolution that could lead to security vulnerabilities.

Improvements

  • Enhanced Debug Logging for Authentication ([log] Add debug logging to auth header parser gh-aw-mcpg#253)
    • Comprehensive debug logging tracks auth header format detection
    • API key validation results logged
    • Missing/malformed headers detected
    • Sensitive data automatically sanitized (only first 4 characters shown)
    • Enable with DEBUG=auth:* environment variable

Code Quality

Impact Assessment

  • Risk: Medium (breaking change in mount path validation)
  • Affected Features:
    • MCP server configurations with mount paths
    • Authentication flows (improved with new package)
    • Debug logging capabilities (enhanced)
  • Migration Required: Yes - update any relative mount paths to absolute paths

Docker Images

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.59
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

Package Links


Files Changed

Modified

  • pkg/constants/constants.go (4 version constants updated)

Requires Recompilation

After merging, run:

make recompile

This will regenerate all workflow YAML files with the new version constants.


Testing Recommendations

  1. Copilot CLI 0.0.382: Run full integration test suite (per WARNING in constants.go)
  2. Codex 0.81.0: Test with new gpt-5.2-codex default model to ensure API compatibility
  3. MCP Gateway v0.0.59:
    • Verify all mount path configurations use absolute paths
    • Test authentication flows with new internal/auth package
    • Verify debug logging works with DEBUG=auth:*

Version Check Details

Check Date: 2026-01-14
Previous Check: 2026-01-06
Tools Checked: 8 (4 updates found, 4 up-to-date)

Up-to-Date Tools

  • GitHub MCP Server: v0.28.1 ✅
  • Playwright MCP: 0.0.55 ✅
  • Sandbox Runtime: 0.0.26 ✅
  • Playwright Browser: v1.57.0 ✅

AI generated by CLI Version Checker

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions