Repository navigation
[deps-release-notes] copilot-cli — upstream release action items #2232
Copy link
Copy link
Closed as not planned
Labels
automationdependenciesPull requests that update a dependency filePull requests that update a dependency file
Description
Rolling upstream release action items — copilot-cli
This is the single canonical tracking issue for action items arising from
new releases of the copilot-cli dependency. The update-awf-version workflow
appends a new comment to this issue for each version bump going forward, so
the most recent activity lives in the comments below. This body is a
consolidated history of everything filed so far.
Latest pinned version covered: 1.0.88
Consolidated history (earliest → latest)
1.0.48 → 1.0.56 (was #803)
- Security: secret scanning covers commit messages + PR descriptions (v1.0.51): Redacts secrets before publishing.
- Security:
permissions.disableBypassPermissionsMode(v1.0.55): Prevents enabling allow-all/yolo mode; relevant for sandboxed pipelines. --session-id=<id>flag (v1.0.51): Resume/start sessions with a specific UUID — useful for pipeline correlation.postToolUsehookadditionalContextinjected as system message (v1.0.49): Instead of being discarded.preMcpToolCallhook (v1.0.51): Control outgoing MCP request metadata.deferred-tool-loadingfrontmatter for custom agents (v1.0.52): Reduces initial token overhead.- MCP tools with both
content+structuredContentsurface both (v1.0.56): Review ado-aw MCP tools to ensure dual output is intentional. - Context window tier selection (v1.0.52): Default ~200K vs 1M tokens enforced end-to-end.
- Claude Opus 4.8 support (v1.0.55).
- Deprecation:
oauth.clientId/oauth.callbackPort→oauthClientId/auth.redirectPort(v1.0.52).
1.0.48 → 1.0.59 (was #843)
- Breaking:
preToolUsehook errors now deny the tool call (v1.0.57): Previously hook errors silently allowed execution; now they block the call. - Breaking: Remote JSON RPC enabled by default (v1.0.58): Verify this doesn't open unexpected network surface in AWF-sandboxed environments.
- Breaking:
--plugin-dirskills take precedence over personal-home skills (v1.0.55): Skill resolution order: project > plugin-dir > personal > custom. - ADO-only repos: built-in GitHub MCP server exposes only
web_search(v1.0.57): Directly relevant to ado-aw; consider whether the GitHub MCP extension should account for ADO-repository detection.
1.0.48 → 1.0.60 (was #881)
- Alpine Linux (musl libc) support (v1.0.49): Now runs on Alpine-based containers.
- Rubber Duck agent enabled by default (v1.0.58): Check whether this adds unexpected turn overhead in automated runs.
1.0.60 → 1.0.61 (was #951)
- Auto-load MCP servers from
.github/mcp.json(v1.0.61): ado-aw uses--additional-mcp-config; consider guarding against auto-loading interference. - Claude Fable 5 model support (v1.0.61): Add to validated models in
src/engine.rs/docs/engine.md. - mTLS + private-CA for OTLP telemetry (v1.0.61): Added
http/protobufOTLP export via OTel env vars. - Bug fix:
grep/globsingle-path fix (v1.0.61): Previously missed results with single path argument. - Bug fix: shell validation false positives (v1.0.61): Fixed blocking of harmless commands with words like "kill" in string literals/heredocs.
1.0.60 → 1.0.62 (was #1002)
- Breaking:
write_bashinteractive input removed (v1.0.62): Shell commands now use lightweight process spawning; interactive input no longer supported. ado-aw exposeswrite_bashas a first-class tool — assess whether tool surface/docs need updating. - Configure subagent model, reasoning effort, context tier (v1.0.62): Consider surfacing
reasoning_effort/context-tier as front-matter fields. - Kerberos/SPNEGO proxy auth (v1.0.62): Auto-auth through corporate forward proxies; relevant for enterprise ADO environments.
1.0.62 → 1.0.63 (was #1057)
deferToolsMCP server config option (v1.0.63): Keeps server tools available even when tool search is enabled. ado-aw could use this for safe-outputs and GitHub MCP servers to prevent them from being filtered out.
1.0.62 → 1.0.64 (was #1183)
- New OTel cache + reasoning token fields (v1.0.64):
gen_ai.usage.cache_read.input_tokens,gen_ai.usage.cache_creation.input_tokens,gen_ai.usage.reasoning.output_tokensper GenAI semconv (old underscore-separated names gone). Updatesrc/agent_stats.rsto parse new attribute names. - Static OAuth client overrides for MCP server auth (v1.0.64): ado-aw could expose in MCP server config front-matter.
- Autopilot mode auto-handles
ask_user, elicitation, sampling, permission prompts (v1.0.64): Reliability improvement for unattended pipeline runs. - Deprecation:
report_intenttool removed (v1.0.64):INTERNAL_TOOL_NAMESexclusion insrc/agent_stats.rscontaining"execute_tool report_intent"is now dead code; can be cleaned up.
1.0.64 → 1.0.67 (was #1272)
- Claude Sonnet 5 model support (v1.0.67): Add to
src/engine.rsmodel allowlist + docs. - Subagent sessions inherit parent tool restrictions (v1.0.67): Security-relevant behavior change; verify against expected security model.
- MCP OAuth against Microsoft Entra vanity domain servers (v1.0.67): Fixes
AADSTSauth failures for Entra vanity domains; relevant for enterprise Azure AD MCP tools. copilot skillsubcommand (v1.0.65): New/skillalias for listing/adding/removing skills; may be relevant for agency plugin scaffolding.- Deprecation: Claude Opus 4.6 Fast → Claude Opus 4.8 Fast (v1.0.66): Update any ado-aw references to
claude-opus-4.6-fast.
1.0.64 → 1.0.68 (was #1305)
- Breaking: session limits require minimum 30 AI credits (v1.0.67): Pipelines with
session-limit:below 30 AI credits will be rejected at runtime. Review compiler defaults. - Claude Opus 4.8 Fast model support (v1.0.66): Add
claude-opus-4.8-fasttosrc/engine.rsallowlist. - kimi-k2.7-code model support (v1.0.68): Add to model allowlist.
1.0.70 → 1.0.81 (was #2041)
- Breaking (v1.0.79): Sandbox settings keys renamed from
sandbox.gitAuth/sandbox.ghAuthtosandbox.auth.git/sandbox.auth.gh, with no migration path. Old keys are silently ignored, and SDK requests using the old keys are rejected as invalid. Any ado-aw-generated engine config or docs referencing the old sandbox setting names need to be updated. See the v1.0.79 release. - Breaking (v1.0.79):
--worktreedefault behavior changed —worktreeBaseRefnow defaults toHEADinstead of the remote default branch. Could change output for any ado-aw workflow relying on worktree creation defaults. See the v1.0.79 release. - Security (v1.0.78): The
/allow-all autosafety-judge model is no longer user-configurable — hardens against downgrade to a weaker safety judge. See the v1.0.78 release. - Security (v1.0.78): Managed-settings fetch failure behavior changed from fail-closed to fail-open — worth confirming this doesn't weaken ado-aw's sandboxed-agent posture when managed settings can't be reached. See the v1.0.78 release.
- Security (v1.0.72): Sandbox macOS keychain access now defaults to off, reducing default credential exposure inside the sandboxed agent. See the v1.0.72 release.
- v1.0.81: Support for MCP protocol version 2026-07-28, OpenTelemetry trace-context propagation (
traceparent/tracestate) into hooks, and per-agent usage metrics via--usage-output-file— could improve ado-aw's OTel-based agent stats correlation (src/agent_stats.rs). See the v1.0.81 release. - v1.0.81: Windows Entra ID broker-based MCP auth (no-prompt sign-in) — relevant if ado-aw ever needs Windows-hosted agent auth flows.
- v1.0.81: Plan mode now hard-blocks mutating tool calls — a safety property ado-aw could rely on/document for plan-only agent configurations.
- v1.0.76/v1.0.77: Enterprise admins can enforce a restrictive sandbox floor and managed sandbox policy via macOS/Windows native MDM — relevant to ado-aw's OneBranch sandboxing story for enterprise consumers. See the v1.0.76 release and v1.0.77 release.
- v1.0.72: Opt-in git/gh auth inside the OS sandbox — worth evaluating against ado-aw's own credential-isolation model (
ado-proxy).
1.0.87 → 1.0.88 (was #2232) — canonical
- None identified. This is a routine point release with terminal/UX and MCP reliability fixes.
- Security: Enterprise managed settings now apply to sessions opened in ACP mode (
copilot --acp), by AHP hosts (copilot --ahp-host), and by the published--serversession, which previously ran with no managed MCP, permission, or plugin policy (v1.0.88). ado-aw invokes the CLI in its default sandboxed one-shot mode, not--acp/--ahp-host/--server, so no immediate action, but worth confirming if any future ado-aw feature drives the CLI through one of those modes. - Security: GitHub MCP scope escalation now uses the CLI OAuth app's registered
/callbackredirect URI (v1.0.88) — tightens an OAuth flow ado-aw does not directly configure. - No notable features identified as directly adoptable by ado-aw in this range. No deprecations identified in this range.
Consolidated by the Deps Release-Notes Consolidator workflow. Superseded per-release issues were closed and point here.> Generated by Deps Release-Notes Consolidator · auto · 74.6 AIC · ⌖ 4.15 AIC · ⊞ 9.6K · ◷
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
automationdependenciesPull requests that update a dependency filePull requests that update a dependency file
Activity
github-actions commentedon Oct 1, 2026
copilot-cli1.0.88→1.0.90Releases analyzed
Breaking changes
Security fixes
--mcp-github-authto scope GitHub account auth to approved MCP server origins (v1.0.90) — restricts which MCP servers can receive the CLI's GitHub account auth token, reducing the blast radius of a misbehaving or malicious MCP server. Worth reviewing whether ado-aw's GitHub MCP extension (src/compile/extensions/github.rs) or user-configured MCP servers should set this flag.Notable features for ado-aw to adopt
.claude/rulescustom instructions support (v1.0.89) — the CLI now reads.claude/rulesas custom instructions; ado-aw could document this as an alternative/companion to its own front-matter prompt composition.create-pull-requestsafe output (prepare-pr-base.js) could consider the same behavior for consistency.claude-opus-5.5, GPT-6 Sol, GPT-6 Luna (v1.0.89), and GPT-6.1 Sol (v1.0.90) — add to the validated model allowlist insrc/engine.rsanddocs/engine.mdif ado-aw wants to support them.Deprecations
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
index.crates.ioTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
github-actions commentedon Oct 2, 2026
copilot-cli1.0.88→1.0.91Releases analyzed
Breaking changes
Fastauto-routing profile (v1.0.89): "Fix Auto tier selection to cycle correctly in/modeland remove the unsupported Fast profile; a previously stored, exported, or resumed Fast preference now falls back to Balance instead of routing on it." Any ado-aw-generated config or docs that reference aFastauto-routing tier should fall back gracefully — verify no front-matter or docs assume this tier still exists.Security fixes
--mcp-github-authflag (v1.0.90): Scopes GitHub account auth to explicitly approved MCP server origins, tightening the blast radius of GitHub credentials exposed to MCP servers. Relevant to ado-aw's GitHub MCP extension — worth evaluating whether ado-aw should set this flag by default for its MCP wiring.copilot sandbox cacommand family (v1.0.91): New commands to check, create, trust, rotate, and remove sandbox proxy CA trust, including unattended Windows setup (/sandbox ca installis now split intocreateandtrust). ado-aw's sandboxed-agent model (AWF + Copilot CLI) should confirm its CA trust story doesn't rely on the old combinedinstallsubcommand if any tooling scripts it.Notable features for ado-aw to adopt
claude-opus-5.5model support (v1.0.89, v1.0.90): New models available in the model picker. Add to the validated-model allowlist insrc/engine.rsanddocs/engine.mdif ado-aw wants to support them..claude/rules) as custom instructions (v1.0.89): CLI now picks up.claude/rulesas custom instructions; relevant if ado-aw ever wants to document cross-tool instruction compatibility.docs/tools.mdstill hold.Deprecations
Fastauto-routing tier removal noted above as a breaking change.github-actions commentedon Oct 6, 2026
copilot-cli1.0.88→1.0.92Releases analyzed
Breaking changes
None identified. No removed flags, renamed config keys, or changed defaults are documented in this range.
Security fixes
GITHUB_TOKENunless explicitly configured (v1.0.92) — reduces default credential exposure inside sandboxed shell commands, continuing the pattern of tightening sandbox credential defaults noted in earlier ranges (e.g. v1.0.72's keychain-access default-off). ado-aw's ownado-proxycredential-isolation model already avoids relying on ambient tokens, so no action expected, but worth confirming no ado-aw-generated step depends on an ambientGITHUB_TOKENbeing present in the sandbox.Notable features for ado-aw to adopt
--mcp-github-authto scope GitHub account auth to approved MCP server origins (v1.0.90) — lets GitHub auth be scoped per-MCP-origin; relevant to how ado-aw wires its GitHub MCP extension and could tighten the auth surface exposed to third-party MCP servers.copilot sandbox cacommands (check/create/trust/rotate/remove) and unattended Windows CA setup (v1.0.91) — new first-class CA-trust management for the sandbox's TLS-inspecting proxy; could simplify ado-aw's docs/tooling for any future corporate-proxy TLS interception scenarios.copilot configsubcommands to list/read/set/remove settings (v1.0.92) — a scriptable settings interface; ado-aw's compiler could use this instead of hand-rolled config-file edits for any future settings-management tooling.Deprecations
None identified in this range.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
index.crates.ioTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
github-actions commentedon Oct 8, 2026
copilot-cli1.0.88→1.0.93Releases analyzed
Breaking changes
/modelAuto cycling (v1.0.89): "Fix Auto tier selection to cycle correctly in /model and remove the unsupported Fast profile; a previously stored, exported, or resumed Fast preference now falls back to Balance instead of routing on it." Any ado-aw docs or defaults referencing a Copilot "Fast" auto-tier should be updated to expect fallback to "Balance".GITHUB_TOKENunless explicitly configured (v1.0.92): tightens default credential exposure inside the CLI's own sandbox. ado-aw already injects its own scoped tokens viaado-proxy/MCPG rather than relying on an ambientGITHUB_TOKEN, so this should be compatible, but worth a spot-check that no ado-aw-generated step depends on an ambientGITHUB_TOKENbeing visible to the Copilot CLI sandbox.~/.copilot/settings.json;~/.copilot/config.jsonuser-setting keys ignored (v1.0.93): if ado-aw's compiled pipelines or docs ever seed~/.copilot/config.jsonto configure CLI behavior, those settings would now be silently ignored — worth confirming no generated step writes config there.Security fixes
permissions.limitToto enforce managed domain boundaries for network requests (v1.0.93): a new enterprise-managed network restriction; complementary to AWF's own network isolation. No action required since ado-aw already enforces network isolation via AWF, but could be documented as an additional enterprise-managed-settings layer.GITHUB_TOKENby default (v1.0.92) — see Breaking changes above; also a security hardening.Notable features for ado-aw to adopt
copilot configsubcommands to list/read/set/remove settings (v1.0.92) — could simplify how ado-aw's generated pipeline steps configure the CLI, replacing any direct file writes to CLI config paths.engine:model allowlist/docs (src/engine.rs,docs/engine.md) should add these newly-available models if ado-aw wants to validate/support them.--mcp-github-authto scope GitHub account auth to approved MCP server origins (v1.0.90) — relevant to ado-aw's GitHub MCP extension; could tighten which MCP servers receive GitHub auth.copilot sandbox cacommands for proxy CA trust management, including unattended Windows setup (v1.0.91) — potentially useful if ado-aw ever needs to manage CLI-level sandbox CA trust for its own AWF/MCPG TLS interception scenarios.Deprecations
~/.copilot/config.jsonuser-setting keys (v1.0.93): superseded by~/.copilot/settings.json; see Breaking changes above.Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
index.crates.ioTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
github-actions commentedon Oct 9, 2026
copilot-cli1.0.88→1.0.94Releases analyzed
Breaking changes
~/.copilot/config.jsonuser-setting keys are now ignored; only~/.copilot/settings.jsonis read (v1.0.93): "Read user settings only from~/.copilot/settings.json; user-setting keys in~/.copilot/config.jsonare ignored." ado-aw doesn't write to either file today, but any docs or troubleshooting guidance that references~/.copilot/config.jsonas a user-settings location should be checked and updated if needed.Security fixes
permissions.limitToenforces managed network domain boundaries (v1.0.93): New enterprise managed-policy control to restrict network requests to an allowed domain set at the CLI level, complementing AWF's own domain allowlisting.--mcp-github-authscopes GitHub account auth to approved MCP server origins (v1.0.90): Limits which MCP servers can receive the CLI's GitHub credentials — relevant to ado-aw's GitHub MCP extension and credential-isolation posture.GITHUB_TOKENunless explicitly configured (v1.0.92): Tightens default credential exposure inside sandboxed shell tool calls, consistent with ado-aw's ownado-proxy/credential-isolation model — worth confirming ado-aw's ownGITHUB_TOKEN/GITHUB_APP_TOKENwiring (src/engine.rs) still behaves as expected with this default.Notable features for ado-aw to adopt
copilot sandbox cacommands (check/create/trust/rotate/remove proxy CA trust, incl. unattended Windows setup) (v1.0.91): Could be referenced in ado-aw's AWF/sandbox troubleshooting docs for diagnosing TLS-interception issues.copilot configsubcommands to list/read/set/remove settings (v1.0.92): Could simplify how ado-aw'srunner-doctor-style diagnostics or docs instruct users to inspect/adjust CLI configuration.--context long_contexthonored at startup, with accurate context allowance shown in/context(v1.0.93): ado-aw'sengine:front-matter could expose acontext-tier/long-context option mapped to this flag for agents needing larger context windows./sandboxand--sandbox(v1.0.93): Broadens sandboxing availability; worth confirming ado-aw's own AWF-level sandboxing doesn't conflict with or duplicate CLI-level sandboxing when both are active.Deprecations
None explicitly announced in this range beyond the
config.json→settings.jsonuser-settings change noted above under Breaking changes.github-actions commentedon Oct 17, 2026
Consolidated into the canonical rolling issue #2322 ( [deps-release-notes] copilot-cli — upstream release action items ). Its action items have been preserved there.