Skip to content

[ca] Update CLI pins: Claude Code 2.1.299, Copilot CLI 1.0.97, MCP Gateway v0.4.31 #68619

Closed as not planned

Description

@github-actions

Overview

CLI Version Checker detected stable updates in run §38517044934 and prepared the corresponding local version constant changes.

Updates detected:

Component Current Latest Source Risk
Claude Code 2.1.296 2.1.299 npm @anthropic-ai/claude-code Low
GitHub Copilot CLI 1.0.96 1.0.97 npm @github/copilot and GitHub release Medium
MCP Gateway v0.4.30 v0.4.31 GitHub release github/gh-aw-mcpg Medium

No updates were needed for Codex, GitHub MCP Server, Playwright CLI, Pi, threat-detect, or the scanner Docker images.

Local changes prepared

  • pkg/constants/version_constants.go
    • DefaultClaudeCodeVersion: 2.1.296 → 2.1.299
    • DefaultCopilotVersion: 1.0.96 → 1.0.97
    • DefaultMCPGatewayVersion: v0.4.30 → v0.4.31
  • pkg/constants/version_constants_test.go updated to match.
  • make recompile completed and regenerated generated workflow locks plus setup compatibility files, including actions/setup/sh/install_copilot_cli.sh and .github/aw/compat.json.

Validation

  • make recompile && echo done: passed; compiled 344/344 workflows.
  • go test ./pkg/constants: passed.
  • make test-unit: passed impacted constants samples.
  • make fmt: Go formatting phase passed, but the JavaScript prettier phase failed because actions/setup/js/node_modules/.bin/prettier was missing.
  • Attempted npm ci --prefix actions/setup/js to install pinned prettier, but npm failed with DEPTH_ZERO_SELF_SIGNED_CERT while fetching a GitHub tarball dependency. Retried with NODE_OPTIONS=--use-system-ca and saw the same certificate failure.

Claude Code 2.1.296 → 2.1.299

Release timeline:

Change analysis:

  • Breaking: none identified from npm metadata or CLI help comparison.
  • Features: none visible in main --help output compared with cached 2.1.296 help.
  • Fixes: no public changelog available; treat as opaque upstream maintenance/fix release.
  • Security: no security notes were available in public npm metadata.
  • Performance: no performance notes were available in public npm metadata.

Impact assessment: Low. gh-aw pins the CLI version and does not rely on newly discovered flags. Help output diff against cached 2.1.296 output showed no command-line surface changes.

Migration requirements: update DefaultClaudeCodeVersion only.

GitHub Copilot CLI 1.0.96 → 1.0.97

Release timeline:

Change analysis:

  • Breaking: none identified. Main help, config help, and environment help match cached 1.0.96 outputs.
  • Features:
    • Agent-scoped declarative hooks for custom agents.
    • Remote plugin marketplace and plugin fetches retry once with the signed-in GitHub token after HTTPS auth fails.
    • Inline images render by default on supported terminals; use /settings inlineImages false to disable.
    • /usage shows billed AI Credits for token-billed sessions, including after resume.
  • Fixes:
    • Streamed responses behind TLS-intercepting proxies complete when close_notify is omitted.
    • GitHub SCP remotes with absolute paths parse correctly for owner/name resolution.
    • Custom agent discovery handles more than 100 agents and deeply nested agent files.
    • Autopilot denies a preToolUse hook ask decision instead of blocking on an unattended permission dialog.
    • Config robustness: invalid config.json entries no longer reset unrelated saved settings.
    • Managed permission rules in /config are read-only and hidden unless set by the organization.
    • view_range timeline/export issues fixed for malformed ranges.
    • Resumed sessions report interrupted tool calls and avoid replaying canceled writes.
    • Explicit GitHub MCP tool/toolset selections use the correct endpoint so requested write tools remain available.
    • Cached MCP tool calls recheck definitions after concurrent catalog refreshes.
    • Plugin-dir skills and custom agents reach autocomplete and invocation.
    • Resumed sessions rebuild plugin hooks from the correct plugin list.
    • Permission recovery retry budgets are tracked per request.
    • Background-shell wait status animation is suppressed when no foreground work is running.
    • Emergency memory relief can bypass cooldown before V8 heap OOM.
  • Security:
    • Redacts secrets safely in --output-format json output while preserving valid variable references.
    • MCP endpoint/toolset fix reduces risk of missing requested tool policy behavior.
  • Performance/reliability:
    • Streaming proxy robustness and emergency memory relief improve long-running agent reliability.

Impact assessment: Medium. The release includes permission, MCP endpoint, plugin hook, config, and JSON redaction changes that are relevant to gh-aw Copilot workflows. No CLI flag changes were found, so migration risk is mostly behavioral/runtime.

Migration requirements: update DefaultCopilotVersion and recompile generated compatibility/install artifacts.

Copilot CLI v1.0.97 release notes
  • Add agent-scoped declarative hooks for custom agents
  • Remote plugin marketplace and plugin fetches retry once with your signed-in GitHub token after HTTPS auth fails.
  • Streamed responses behind TLS-intercepting proxies complete when close_notify is omitted
  • Fix parsing of GitHub SCP remotes with absolute paths so repository owner and name resolve correctly
  • Discover all custom agents even when repositories define more than 100 or nest agent files deeply.
  • Autopilot denies a preToolUse hook's ask decision instead of stopping on a permission dialog nobody is watching
  • Keep Windows taskbar agent icons grouped across CLI updates by using a stable icon path
  • Keep saved settings such as dismissed prompts, trusted folders and sign-ins when one entry in config.json is invalid, instead of resetting them on every launch
  • In /config, managed permission rules are read-only and hidden unless set by your organization.
  • Show billed AI Credits in /usage for token-billed sessions, including after resume
  • File reads using a view_range that is not exactly two elements, such as a lone start line, now show their line range and line count in the timeline, and session exports no longer contain the literal text undefined
  • Dragging to select text in the transcript no longer occasionally highlights and copies the row below the pointer.
  • Power BI and Bluebird MCP servers accept their published resource scopes during sign-in
  • Redact secrets safely in --output-format json output while preserving valid variable references
  • Resuming suspended sessions now reports interrupted tool calls and avoids replaying canceled writes.
  • Synchronous /task JSON output now includes failed child error and lifecycle events before completion.
  • Explicit GitHub MCP tool and toolset selections use the correct endpoint, so requested write tools stay available.
  • Cached MCP tool calls recheck their definition when a concurrent tool-list refresh changes the catalog.
  • Skills and custom agents from --plugin-dir plugins now reach autocomplete and invocation instead of going missing.
  • Fixed resumed sessions rebuilding plugin hooks from the wrong plugin list, so hooks from repository-local marketplace plugins now keep running after --resume, and hooks from plugins your configuration disabled no longer come back
  • Keep /user switch new-session choices visible after account checks in short terminals
  • Unavailable permission recovery attempts are now tracked per request, so unrelated calls no longer consume each other's retry budget.
  • Background-shell wait status no longer animates when no foreground work is running
  • Emergency memory relief in long sessions can now bypass its cooldown before V8 aborts, so a session that would have been killed by a JavaScript heap out of memory crash may survive with compacted history instead
  • Inline images render by default on supported terminals without enabling experimental mode. Use /settings inlineImages false to turn them off

MCP Gateway v0.4.30 → v0.4.31

Release timeline:

Change analysis:

  • Breaking: none called out in release notes.
  • Features/refactors:
    • Centralized Rust guard tool-name constants, including codespace, gist, deploy-key, GPG/SSH key, workflow-toggle, and repository lifecycle/write-tool names.
    • Additional guard coverage for gh gist rename.
  • Fixes:
    • Classifies gh gist rename as a write with user-scoped labels.
    • Adds regression coverage for repository lifecycle writes.
    • Adds tests around shutdown tracing provider timeout, config normalization, enclave session detection, proxy URL rewriting, override-to-public-scope, and command execution.
  • Security:
    • Guard classification and write-tool centralization are security-relevant because they affect MCP Gateway command/tool policy enforcement.
  • Performance: no performance-specific changes identified.

Impact assessment: Medium. MCP Gateway is used as a default sandbox.agent container; the guard write-tool classification improvements are relevant to workflow isolation and policy correctness. The release is very recent, so extra runtime smoke coverage is recommended before broad rollout.

Migration requirements: update DefaultMCPGatewayVersion and recompile generated workflow locks.

MCP Gateway v0.4.31 notable release entries

Docker image digest check

Scanner image digests were resolved and matched the pinned values in pkg/cli/docker_images.go:

Constant Selected tag Digest status
ZizmorImage 1.30.1 unchanged sha256:a2eb396d886c053073405c7a980f2139ba2248ec172243cfa3841e57196e8101
PoutineImage 1.1.6 unchanged sha256:722a8e0999b583c1540fe2974e691032b2d9d21b9256a17965132b6bfd0081b0
RunnerGuardImage 3.1.5 unchanged sha256:2df426ef96d21f1622e05b21329f26bd263fc46110609cefb6afe43457613ac0
ActionlintImage 1.7.12 unchanged sha256:b1934ee5f1c509618f2508e6eb47ee0d3520686341fec936f3b79331f9315667
SyftImage v1.54.1 unchanged sha256:3eb5379ba7b409c3f4069b686110527af0c47df993fa5c10d13e7cf34f49b1aa
GrypeImage v0.120.1 unchanged sha256:e4a44ef45d285b829ce6efe2642980329661bd2d18eab5fc539138d4adaebbbe
GrantImage v0.6.8 unchanged sha256:172463611795f43b77302cdfbd7b3f81295492a7330e0820cfe41c3674920237
YamllintImage latest unchanged sha256:f7f7b4f8824839e33690a880dbe20944128b0dc9c55522a0b92a29b3a905cecf

GitHub release checks found no newer stable scanner releases that passed the applicable criteria; PipelineComponents/yamllint latest release endpoint returned 404, so the existing latest tag digest was checked directly.

Unchanged components

  • Codex: current 0.162.1, latest 0.162.1.
  • GitHub MCP Server: current v2.0.2, latest v2.0.2.
  • Playwright CLI: current 0.1.22, latest 0.1.22.
  • Pi: current 1.2.0, latest 1.2.0.
  • Threat-detect: current v0.5.2, latest v0.5.2.

Next actions

  1. Review the prepared constants and generated recompile output.
  2. Resolve the local npm certificate issue so make fmt can complete its JavaScript prettier phase.
  3. Run final repository validation after prettier dependencies are available.
  4. Give extra smoke-test attention to Copilot MCP/toolset selection and MCP Gateway guard/write classification paths.

References:

Generated by 🔢 CLI Version Checker · pi · gpt55 · 182.6 AIC · ⌖ 20.5 AIC · ⊞ 11.3K · ◷

  • expires on Oct 15, 2026, 9:42 PM UTC-08:00

Activity

  1. github-actions commented on Oct 15, 2026

    @github-actions
    ContributorAuthor

    🍪 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 · pi · gpt54 · 11.9 AIC · ⌖ 7.92 AIC · ⊞ 11.9K · ◷

  2. github-actions commented on Oct 15, 2026

    @github-actions
    ContributorAuthor

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

    View newer issue


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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    automationcookieIssue Monster Loves Cookies!dependenciesPull requests that update a dependency file

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions