Skip to content

[deps-release-notes] copilot-cli v1.0.59 action items #843

@github-actions

Description

@github-actions

Release Notes Action Items for copilot-cli 1.0.481.0.59

This issue summarizes upstream release notes for the copilot-cli dependency between the previously pinned version (1.0.48) and the new pinned version (1.0.59), highlighting items that may need follow-up in ado-aw.

The companion version-bump PR is titled chore(deps): update COPILOT_CLI_VERSION to 1.0.59.

Releases analyzed

Breaking changes

  • preToolUse hook errors now deny the tool call instead of silently allowing execution (v1.0.57) — behavior change for agents using preToolUse hooks; previously a hook error would silently allow the tool call to proceed, now it blocks it. Any ado-aw pipelines relying on the old permissive behavior will behave differently. (v1.0.57)
  • Remote JSON RPC is now enabled by default (v1.0.58) — the remote JSON RPC transport is now on by default; existing deployments that relied on it being disabled by default may need to account for the new default. (v1.0.58)
  • --plugin-dir skills now take precedence over personal-home skills (v1.0.55) — skill resolution order changed to: project > plugin-dir > personal > custom. Pipelines that mount both plugin-dir and home-based skills may see different skill selection. (v1.0.55)

Notable features for ado-aw to adopt

  • In Azure DevOps-only repositories, the built-in GitHub MCP server now exposes only the web_search tool instead of being fully disabled (v1.0.57) — directly relevant to ado-aw: consider whether the ado-aw GitHub MCP extension should be updated to account for or leverage this ADO-repository detection behavior. (v1.0.57)
  • When gh CLI is on PATH, GitHub MCP server omits redundant gh-replaceable tools by default, reducing token usage (v1.0.56) — ado-aw pipelines that include gh CLI may benefit from reduced token consumption without any code changes, but worth verifying expected tool availability. (v1.0.56)
  • permissions.disableBypassPermissionsMode setting prevents enabling allow-all/yolo mode (v1.0.55) — a new security policy setting worth surfacing in ado-aw's compiler or documentation so pipeline authors can lock down agent permissions. (v1.0.55)
  • MCP tools returning both contenttext andstructuredContent now surface both to the agent (v1.0.56) — ado-aw MCP tools should be reviewed to ensure their structured + text output is intentional; previously one side may have been silently dropped. (v1.0.56)
  • /voice command added to dictate prompts using local speech-to-text (v1.0.59) — new interactive capability; low immediate impact on ado-aw since it targets non-interactive pipeline agents, but worth awareness. (v1.0.59)

This issue was opened automatically by the dependency version updater workflow.

Generated by Dependency Version Updater · sonnet46 1.9M ·

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions