chore: bump @github/copilot to 1.0.76-2 - #327992
chore: bump @github/copilot to 1.0.76-2#327992vs-code-engineering[bot] wants to merge 2 commits into
Conversation
vs-code-engineering
Bot
added
the
copilot-sdk-auto-upgrade
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.
Bumps the @github/copilot dependency version in both the root and remote packages.
Changes:
- Updated
@github/copilotfrom^1.0.73to^1.0.76-2inpackage.json - Updated
@github/copilotfrom^1.0.73to^1.0.76-2inremote/package.json
Reviewed changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| package.json | Updates the root app’s @github/copilot dependency to a newer prerelease build. |
| remote/package.json | Keeps the remote package aligned with the root by updating @github/copilot similarly. |
Files not reviewed (1)
- remote/package-lock.json: Generated file
| "dependencies": { | ||
| "@anthropic-ai/sdk": "^0.82.0", | ||
| "@github/copilot": "^1.0.73", | ||
| "@github/copilot": "^1.0.76-2", |
| "private": true, | ||
| "dependencies": { | ||
| "@github/copilot": "^1.0.73", | ||
| "@github/copilot": "^1.0.76-2", |
|
🏗️ Product build queued for cycle 1: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=459871 — validating the PR branch… |
|
❌ Product build against the PR branch — cycle 1:
|
CLI 1.0.76-2 adds a nested framework binary at extensions/copilot/node_modules/@github/copilot/sdk/prebuilds/darwin-arm64/ mediaremote-adapter/MediaRemoteAdapter.framework/MediaRemoteAdapter. The x64ArchFiles rule matched the copilot sdk prebuilds only one level deep (prebuilds/darwin-*/*), so this deeper binary was not covered and the universal merge failed with "same in both x64 and arm64 builds and not covered by the x64ArchFiles rule". Broaden the prebuilds entries to /**, matching how filesToSkip and singleArchFiles already treat these dirs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Commit pushed:
|
|
Fixed & pushed: the Create Universal App packaging failure. CLI 1.0.76-2 adds a nested framework binary ( Upstream-blocked (needs decision): the 3
No VS Code edit can make a protocol-incompatible pair handshake. Recommendation: hold this CLI-only bump until a compatible SDK (carrying the copilot-sdk#2118 protocol change) is published, then re-run as a combined SDK+CLI bump. Full analysis is in the PR body status island. Leaving the PR as draft.
|
|
🏗️ Product build queued for cycle 2: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=459884 — validating the PR branch… |
|
❌ Product build against the PR branch — cycle 2:
|
Automated signed Copilot dependency bump.
@github/copilot:^1.0.73→^1.0.76-2main@d790d7d957f685337ab8a7f15e6dbd74f4ffe139Draft 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.73 → 1.0.76-2No published path changes.
@github/copilot-darwin-x641.0.73 → 1.0.76-2plugins/computer-use/.mcp.jsonplugins/computer-use/.plugin/plugin.jsonplugins/computer-use/Copilot Computer Use.app/Contents/CodeResourcesplugins/computer-use/Copilot Computer Use.app/Contents/Info.plistplugins/computer-use/Copilot Computer Use.app/Contents/MacOS/Copilot Computer Useplugins/computer-use/Copilot Computer Use.app/Contents/PkgInfoplugins/computer-use/Copilot Computer Use.app/Contents/Resources/Assets.carplugins/computer-use/Copilot Computer Use.app/Contents/Resources/icon.icnsplugins/computer-use/Copilot Computer Use.app/Contents/_CodeSignature/CodeResourcesplugins/computer-use/computer-use-mcpprebuilds/darwin-x64/mediaremote-adapter/LICENSEprebuilds/darwin-x64/mediaremote-adapter/MediaRemoteAdapter.framework/MediaRemoteAdapterbuiltin-plugins/computer-use/0.1.71/darwin-x64/.mcp.jsonbuiltin-plugins/computer-use/0.1.71/darwin-x64/.plugin/plugin.jsonbuiltin-plugins/computer-use/0.1.71/darwin-x64/Copilot Computer Use.app/Contents/CodeResourcesbuiltin-plugins/computer-use/0.1.71/darwin-x64/Copilot Computer Use.app/Contents/Info.plistbuiltin-plugins/computer-use/0.1.71/darwin-x64/Copilot Computer Use.app/Contents/MacOS/Copilot Computer Usebuiltin-plugins/computer-use/0.1.71/darwin-x64/Copilot Computer Use.app/Contents/PkgInfobuiltin-plugins/computer-use/0.1.71/darwin-x64/Copilot Computer Use.app/Contents/Resources/Assets.carbuiltin-plugins/computer-use/0.1.71/darwin-x64/Copilot Computer Use.app/Contents/Resources/icon.icnsbuiltin-plugins/computer-use/0.1.71/darwin-x64/Copilot Computer Use.app/Contents/_CodeSignature/CodeResourcesbuiltin-plugins/computer-use/0.1.71/darwin-x64/computer-use-mcp@github/copilot-linux-x641.0.73 → 1.0.76-2No published path changes.
@github/copilot-win32-x641.0.73 → 1.0.76-2plugins/computer-use/.mcp.jsonplugins/computer-use/.plugin/plugin.jsonplugins/computer-use/CopilotComputerUse.exeplugins/computer-use/computer-use-mcp.exebuiltin-plugins/computer-use/0.1.71/win32-x64/.mcp.jsonbuiltin-plugins/computer-use/0.1.71/win32-x64/.plugin/plugin.jsonbuiltin-plugins/computer-use/0.1.71/win32-x64/CopilotComputerUse.exebuiltin-plugins/computer-use/0.1.71/win32-x64/computer-use-mcp.exeSDK/CLI bump fix status — cycle 1
SDK+CLI correlation: SDK
1.0.8(unchanged, declares CLI range^1.0.73→ covers1.0.76-2) + CLI1.0.76-2. This is a CLI-only bump;sdk-compatibility.mdconfirms SDK 1.0.8 is compatible with this CLI, so no SDK bump escalation. The canary Slack insights are for a different CLI (1.0.76-canary.24/ SDK1.0.9-canary.28) — treated as a hypothesis, confirmed below against this exact signed pair's product build 459871.Two failure classes in product build 459871
1. Create Universal App (macOS UNIVERSAL) — FIXED ✅
CLI 1.0.76-2 introduced a newly-nested framework binary at
extensions/copilot/node_modules/@github/copilot/sdk/prebuilds/darwin-arm64/mediaremote-adapter/MediaRemoteAdapter.framework/MediaRemoteAdapter. Thex64ArchFilesallow-rule inbuild/darwin/create-universal-app.tsmatched copilot-sdk prebuilds only one directory deep (prebuilds/darwin-*/*), so this deeper binary was uncovered and the fat-binary merge rejected it. Broadened the prebuilds entries toprebuilds/darwin-*/**(matching howfilesToSkipandsingleArchFilesalready treat these dirs). Verified locally with the repo'sminimatch: the new rule matches the nested framework binary and still matches the shallow prebuilds. Pushed this cycle.2. CopilotAgent unit tests (3, all OSes) — UPSTREAM-BLOCKED⚠️ (needs reviewer decision)
Three tests that spawn the real pinned CLI fail deterministically on macOS-ARM64, Linux-X64, and Windows-X64 with
Error: CLI server exited unexpectedly with code 0at@github/copilot-sdk/dist/cjs/client.js:1839. The CLI process exits cleanly (code 0) with no stderr — the SDK's stdio server handshake never completes. This is an SDK↔CLI runtime/protocol incompatibility, not a VS Code integration bug:main(src/vs/platform/agentHost/**is identical); the only delta is the CLI pin1.0.73→1.0.76-2. All prior CLI bumps were lockfile-only._ensureClient(--headless --no-auto-update --stdio --no-auto-login,RuntimeConnection.forStdio) still exist and are correct in 1.0.76-2.sdk-compatibility.md): the SDK's own cross-platform E2E canary for the CLI 1.0.76 base (1.0.76-canary.24) fails on Linux, macOS, and Windows; the SDK dependency/protocol-update PR copilot-sdk#2118 is an open draft (not merged/published); and the version thread notes the agent-runtime protocol fix (copilot-agent-runtime#13634) is "not in npm yet." No published SDK yet carries the protocol change this CLI requires.Per the bump-fix classification rules, this is the "waiting on upstream SDK work / publication" case: no VS Code edit can make a protocol-incompatible SDK/CLI pair handshake. The likely resolution is to hold this CLI-only bump until a compatible SDK (carrying the copilot-sdk#2118 protocol change) is published, then re-run as a combined SDK+CLI bump.
Independent, verified Universal App packaging fix pushed this cycle to reduce the failing surface; the unit-test failure is isolated and escalated to reviewers.
SDK/CLI bump fix status — cycle 2
Product build 459884 confirms cycle 1's diagnosis and packaging fix. The build now fails on only the 3
CopilotAgentunit tests; the Create Universal App task that cycle 1 fixed (build/darwin/create-universal-app.tsprebuilds globs →/**) no longer fails — the packaging fix is validated against this exact signed pair.SDK+CLI correlation (re-confirmed against the signed pair): SDK
1.0.8(latest published, declares CLI floor^1.0.73) + CLI1.0.76-2. Semver-compatible on paper, but the runtime handshake is not — so this is not an SDK-bump-available case (no newer SDK is published that carries the protocol change).Sole remaining failure — UPSTREAM-BLOCKED⚠️ (unchanged from cycle 1): the 3 tests spawn the real pinned CLI and fail deterministically on macOS-ARM64, Linux-X64, and Windows-X64 with
Error: CLI server exited unexpectedly with code 0at@github/copilot-sdk/dist/cjs/client.js:1839. The CLI subprocess exits cleanly (code 0) with no stderr — the SDK's stdio server handshake never completes. This is an SDK↔CLI runtime/protocol incompatibility, not a VS Code integration bug:main—src/vs/platform/agentHost/**is byte-identical; the only change is the CLI pin1.0.73→1.0.76-2.RuntimeConnection.forStdio), not the koffi FFI transport, so no payload-strip/packaging edit applies.sdk-compatibility.md): the SDK's own cross-platform E2E canary for the CLI 1.0.76 base fails on Linux/macOS/Windows; the SDK protocol-update PR copilot-sdk#2118 is an open draft (not merged/published); the agent-runtime protocol fix (copilot-agent-runtime#13634) is "not in npm yet."No integration change to push this cycle — no VS Code edit can make a protocol-incompatible SDK/CLI pair handshake, and every independently-fixable failure (Universal App packaging) is already landed and confirmed green. Smallest unresolved human task: hold this CLI-only bump until a compatible SDK carrying the copilot-sdk#2118 protocol change is published, then re-run as a combined SDK+CLI bump. Reviewers were already pinged in cycle 1 with the same blocker; PR remains a draft. Current product-build state: cycle 2 (build 459884) failed on the upstream-blocked unit tests only.