chore: bump @github/copilot to 1.0.81-3 - #331627
chore: bump @github/copilot to 1.0.81-3#331627vs-code-engineering[bot] wants to merge 3 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
Note
Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.
Updates the @github/copilot dependency version across the root and remote packages.
Changes:
- Bump
@github/copilotfrom1.0.81-0to1.0.81-3inpackage.json - Bump
@github/copilotfrom1.0.81-0to1.0.81-3inremote/package.json
Reviewed changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Updates root dependency version for @github/copilot to 1.0.81-3. |
| remote/package.json | Keeps the remote package aligned by updating @github/copilot to 1.0.81-3. |
Files not reviewed (1)
- remote/package-lock.json: Generated file
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
🏗️ Product build queued for cycle 1: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=465914 — validating the PR branch… |
|
❌ Product build against the PR branch — cycle 1:
|
…ojection The bumped @github/copilot CLI now prepends a one-turn <tools_changed_notice> block to the next user message when a tool (exit_plan_mode) is withdrawn after plan approval. This block is runtime-authored and environment/timing-derived, not host structure, so elide it (along with the sibling working_directory_changed and additional_directories_changed notices) symmetrically on both recorded and live requests before comparison. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Commit pushed:
|
|
🏗️ Product build queued for cycle 2: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=465930 — validating the PR branch… |
|
❌ Product build against the PR branch — cycle 2:
|
The @github/copilot 1.0.81-3 runtime now advertises the MCP `sampling` client capability to plugin MCP servers only when the session has a live consumer registered for the `sampling.requested` event. VS Code drives sampling via rpc.mcp.executeSampling, which no longer implicitly counts as a consumer, so plugin servers were told "sampling is not supported by this client" and createMessage() failed. Register interest explicitly on session init and release it on dispose. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Commit pushed:
|
|
🏗️ Product build queued for cycle 3: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=465933 — validating the PR branch… |
|
❌ Product build against the PR branch — cycle 3:
|
|
Closing this automated Copilot SDK/CLI bump PR: it has been open for more than a week and newer signed versions have since been targeted by |
Automated signed Copilot dependency bump.
@github/copilot:1.0.81-0→1.0.81-3main@0dac2a8dfdad732e464a588028ac89cdb55cb988Draft until validation passes. The
sdk-vscode-bump-fixagent will prime packaging changes from the canary insights and iterate on failures.Each product build triggered for this PR is posted as a comment below with a link.
Published package layout changes
Copilot published package layout diff
Best-effort path comparison from
npm pack --dry-run; CLI platform paths use representative x64 packages for macOS, Linux, and Windows. Content-only and architecture-specific changes are left to the product build. This is not an availability gate.@github/copilot1.0.81-0 → 1.0.81-3No published path changes.
@github/copilot-darwin-x641.0.81-0 → 1.0.81-3prebuilds/darwin-x64/copilot-runtimeclipboard/index.jsclipboard/node_modules/@teddyzhu/clipboard-darwin-x64/README.mdclipboard/node_modules/@teddyzhu/clipboard-darwin-x64/clipboard.darwin-x64.nodeclipboard/node_modules/@teddyzhu/clipboard-darwin-x64/package.jsonclipboard/node_modules/@teddyzhu/clipboard/LICENSEclipboard/node_modules/@teddyzhu/clipboard/README.mdclipboard/node_modules/@teddyzhu/clipboard/clipboard.darwin-arm64.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.darwin-x64.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.linux-arm64-gnu.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.linux-x64-gnu.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.win32-arm64-msvc.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.win32-x64-msvc.node@github/copilot-linux-x641.0.81-0 → 1.0.81-3prebuilds/linux-x64/copilot-runtimeclipboard/index.jsclipboard/node_modules/@teddyzhu/clipboard-linux-x64-gnu/README.mdclipboard/node_modules/@teddyzhu/clipboard-linux-x64-gnu/clipboard.linux-x64-gnu.nodeclipboard/node_modules/@teddyzhu/clipboard-linux-x64-gnu/package.jsonclipboard/node_modules/@teddyzhu/clipboard/LICENSEclipboard/node_modules/@teddyzhu/clipboard/README.mdclipboard/node_modules/@teddyzhu/clipboard/clipboard.darwin-arm64.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.darwin-x64.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.linux-arm64-gnu.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.linux-x64-gnu.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.win32-arm64-msvc.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.win32-x64-msvc.node@github/copilot-win32-x641.0.81-0 → 1.0.81-3prebuilds/win32-x64/copilot-runtime.execlipboard/index.jsclipboard/node_modules/@teddyzhu/clipboard-win32-x64-msvc/README.mdclipboard/node_modules/@teddyzhu/clipboard-win32-x64-msvc/clipboard.win32-x64-msvc.nodeclipboard/node_modules/@teddyzhu/clipboard-win32-x64-msvc/package.jsonclipboard/node_modules/@teddyzhu/clipboard/LICENSEclipboard/node_modules/@teddyzhu/clipboard/README.mdclipboard/node_modules/@teddyzhu/clipboard/clipboard.darwin-arm64.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.darwin-x64.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.linux-arm64-gnu.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.linux-x64-gnu.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.win32-arm64-msvc.nodeclipboard/node_modules/@teddyzhu/clipboard/clipboard.win32-x64-msvc.node🔧 sdk-vscode-bump-fix status (cycle 1)
Root cause (regression class: intentional runtime contract change). The bumped
@github/copilotCLI (1.0.81-3) now prepends a one-turn<tools_changed_notice>block to the next user message when a tool is withdrawn mid-session — hereexit_plan_modeis removed after the plan is approved. The Agent Host E2E capi-replay test "planning-mode session-state writes are auto-approved in default mode" failed on Windows(X64) and macOS(ARM64) withmodel request #5 does not match the recorded request in the fixture, because the live request #5 carried the notice while the recorded fixture did not. Confirmed runtime-authored (prompts/cli_user::tools_changed_notice, sibling toworking_directory_changed/additional_directories_changed), not VS Code product code.Fix. Elided the runtime-injected change-notice blocks (
tools_changed_notice,working_directory_changed,additional_directories_changed) symmetrically in the capi-replay projection (modelRequestProjection.ts), so both recorded and live user messages compare equal. These blocks are environment/timing-derived, not host-authored structure, matching the existing elision policy for tool-result payloads, runtime ids, and paths. No fixture regeneration; no build/packaging/signing changes.SDK+CLI correlation. CLI-only bump. SDK on branch
1.0.11declares CLI range^1.0.79(floor1.0.79) persdk-compatibility.md— this bump's CLI1.0.81-3is in range, so no paired-SDK bump is required. The failing canary threads use a different CLI (1.0.81-canary.*); their native-payload verdicts do not apply to this exact signed pair.Product-build state. Pushed harness fix; awaiting the next
sdk-vscode-bump-validateproduct build for authoritative validation.> Generated by sdk-vscode-bump-fix · opus48 · 324.6 AIC · ⌖ 23.4 AIC · ⊞ 18K · ◷🔧 sdk-vscode-bump-fix status (cycle 2)
Root cause (regression class: intentional runtime contract change). The bumped
@github/copilotCLI (1.0.81-3) changed the MCP client-capability contract: the runtime now advertises the MCPsamplingcapability to a plugin MCP server only when the session has a live consumer registered for thesampling.requestedevent. VS Code drives sampling exclusively throughrpc.mcp.executeSampling(App→host(redacted) channel), which no longer implicitly counts as a consumer. Without a registered interest, plugin servers receivedMcpError -32603: ... sampling is not supported by this client, soserver.createMessage()threw. The Agent Host E2E test *"plugin MCP sampling cancellation returns to the model"* failed on all platforms because the tool-result carried the McpError string instead of the expectedMCP_SAMPLE:The user cancelled the request.. Confirmed against runtime source:native_session.rsderive_client_capabilitiesgatessamplingonactive_session_has_event_interest(session_id, "sampling.requested"), andrpc.rsdocuments that long-polling SDK clients must explicitlyregisterInterest` for each gated event type.Fix. In
copilotAgentSession.ts, register interest insampling.requested(session.rpc.eventLog.registerInterest({ eventType: 'sampling.requested' })) duringinitializeSessionand release the returned handle on dispose (guarded for the race where the session is disposed mid-registration). Scoped to sampling — the only capability failing this build. No fixture regeneration; no build/packaging/signing changes.SDK+CLI correlation. CLI-only bump. SDK on branch
1.0.11declares CLI range^1.0.79; this bump's CLI1.0.81-3is in range, so no paired-SDK bump is required. Failing canary threads use a different CLI (1.0.81-canary.*); their native-payload verdicts do not apply to this exact signed pair — this is a genuine integration contract change VS Code must adopt.Local validation. Full
typecheck-clientOOMs in this sandbox; a scopedtscovercopilotAgentSession.tsreports no errors on the changed code (the SDKrpc.eventLog.registerInterest/releaseInteresttypes match the existingrpc.mcp.executeSamplingaccess path). The e2e replay test requires a full product build + live runtime, deferred to the authoritative build.Product-build state. Pushed the product fix; awaiting the next
sdk-vscode-bump-validateproduct build for authoritative validation.> Generated by sdk-vscode-bump-fix · opus48 · 754.9 AIC · ⌖ 23.7 AIC · ⊞ 18K · ◷