Skip to content

chore: bump @github/copilot to 1.0.76-0 - #327743

Draft
vs-code-engineering[bot] wants to merge 1 commit into
mainfrom
automation/bump-copilot-cli-1.0.76-0
Draft

chore: bump @github/copilot to 1.0.76-0#327743
vs-code-engineering[bot] wants to merge 1 commit into
mainfrom
automation/bump-copilot-cli-1.0.76-0

Conversation

@vs-code-engineering

@vs-code-engineering vs-code-engineering Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

SDK bump fix status — sdk-bump-waiting-upstream (cycle 1, re-validated on build 459423)

No integration changes needed / pushed. This remains an upstream SDK↔CLI contract gap that no VS Code edit can close.

SDK+CLI correlation: pins SDK 1.0.8 + CLI 1.0.76-0. Published SDK 1.0.8 declares CLI range ^1.0.73 (floor 1.0.73) and does not declare/support CLI 1.0.76. No published SDK whose CLI floor reaches 1.0.76 exists (only 1.0.8^1.0.73 and 1.0.8-preview.0^1.0.72). The exact same-base SDK canary 1.0.76-canary.24 failed E2E on all three platforms.

**Root cause (re-confirmed on product build [459423]((dev.azure.com/redacted) identical signature to build 459275 — 6 smoke timeouts across the SDK-client editor / Agents Window sessions for both Copilot CLI and Claude (incl. terminal variants). Decisively, Test Copilot CLI session via AgentHost PASSES — that route drives CLI 1.0.76 over RuntimeConnection.forStdio against the external @github/copilot-sdk 1.0.8, so native payloads / koffi / stdio protocol are healthy. Only sessions consuming the CLI package's own bundled @github/copilot/sdk (v1.0.76) wedge — an SDK↔CLI turn-lifecycle/protocol mismatch the same-base canary reproduces upstream, not a VS Code integration bug.

Why no VS Code fix: the only adaptable surface (extensions/copilot) is frozen/maintenance-mode (pins must not change); version pins & lockfiles are off-limits for this class; published-package layout diff shows no path/payload changes, so it is not a packaging/strip fix.

Upstream delta since cycle 1: SDK dependency-update PR github/copilot-sdk#2100 moved from draft → open but is still unmerged (unstable, CI running) and no compatible SDK has been published.

Human action required: land + publish an @github/copilot-sdk whose declared CLI floor reaches 1.0.76 (tracked by github/copilot-sdk#2100), then re-run this as a combined SDK+CLI bump (replacing this CLI-only branch). PR left draft.

Generated by sdk-vscode-bump-fix · opus48 · 245.3 AIC · ⌖ 17.1 AIC · ⊞ 17.8K ·

@vs-code-engineering vs-code-engineering Bot added the copilot-sdk-auto-upgrade Automated Copilot SDK/CLI version-bump PR label Jul 27, 2026
Copilot AI review requested due to automatic review settings July 27, 2026 23:48
@vs-code-engineering vs-code-engineering Bot added the copilot-sdk-auto-upgrade Automated Copilot SDK/CLI version-bump PR label Jul 27, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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/copilot from ^1.0.73 to ^1.0.76-0 in the root package.json
  • Bump @github/copilot from ^1.0.73 to ^1.0.76-0 in remote/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 @github/copilot dependency version to a pre-release build.
remote/package.json Mirrors the same @github/copilot version bump in the remote package.
Files not reviewed (1)
  • remote/package-lock.json: Generated file

Comment thread package.json
"dependencies": {
"@anthropic-ai/sdk": "^0.82.0",
"@github/copilot": "^1.0.73",
"@github/copilot": "^1.0.76-0",
Comment thread remote/package.json
"private": true,
"dependencies": {
"@github/copilot": "^1.0.73",
"@github/copilot": "^1.0.76-0",
@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

🏗️ Product build queued for cycle 1: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=459275 — validating the PR branch…

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

Product build against the PR branch — cycle 1: failed

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

🚧 Copilot CLI bump 1.0.76-0 blocked on upstream SDK — human action needed

@pwang347 @anthonykim1 — this CLI-only bump cannot go green from VS Code changes alone; it's waiting on upstream SDK work.

Root cause

This PR pins SDK 1.0.8 + CLI 1.0.76-0, but published SDK 1.0.8 declares CLI range ^1.0.73 and does not support 1.0.76. The exact same-base SDK canary 1.0.76-canary.23 failed E2E on all three platforms (Linux/macOS/Windows), and the SDK dependency-update PR github/copilot-sdk#2100 is still an open draft — no published SDK whose CLI floor reaches 1.0.76 exists yet.

The failing product build (459275) shows 6 smoke timeouts across the SDK-client editor / Agents Window sessions (Copilot CLI and Claude, incl. terminal variants). Decisively, Test Copilot CLI session via AgentHost passes — that route drives CLI 1.0.76 over RuntimeConnection.forStdio against the external @github/copilot-sdk 1.0.8, proving the native payloads/koffi/stdio protocol are healthy. Only the sessions consuming the CLI package's own bundled @github/copilot/sdk (v1.0.76) hang — an SDK↔CLI contract mismatch the same-base canary already reproduces upstream, not a VS Code integration bug.

Why no fix was pushed

  • The only adaptable surface, extensions/copilot, is frozen (maintenance mode) — its pins must not change.
  • Version pins / lockfiles are off-limits for this failure class per the bump workflow.
  • Published-package layout diff shows no path/payload changes, so this isn't a packaging/strip fix.

Requested action

Land + publish an @github/copilot-sdk whose declared CLI floor reaches 1.0.76 (tracked by github/copilot-sdk#2100), then re-run this as a combined SDK+CLI bump (replacing this CLI-only branch). Leaving the PR draft. No code was pushed (cycle 1).

Generated by sdk-vscode-bump-fix · opus48 · 569.9 AIC · ⌖ 17.7 AIC · ⊞ 17.8K ·

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

🏗️ Product build queued for cycle 1: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=459423 — validating the PR branch…

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

Product build against the PR branch — cycle 1: failed

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

🔁 Product build 459423 reproduces the identical upstream blocker — no VS Code integration fix is possible, so nothing was pushed this cycle.

Same signature as build 459275: 6 smoke timeouts on the SDK-client editor / Agents Window sessions for both Copilot CLI and Claude, while Test Copilot CLI session via AgentHost PASSES. The passing AgentHost route drives CLI 1.0.76 over RuntimeConnection.forStdio against external @github/copilot-sdk 1.0.8 (native payloads/koffi/stdio healthy); only sessions using the CLI's bundled @github/copilot/sdk v1.0.76 hang → SDK↔CLI turn-lifecycle mismatch.

Published SDK 1.0.8 declares CLI floor ^1.0.73 and does not reach 1.0.76; no compatible SDK is published. The dependency-update PR github/copilot-sdk#2100 is still open/unmerged.

Action needed (unchanged): land + publish an @github/copilot-sdk whose CLI floor reaches 1.0.76, then re-run as a combined SDK+CLI bump. PR remains draft.

@pwang347 @anthonykim1

Generated by sdk-vscode-bump-fix · opus48 · 245.3 AIC · ⌖ 17.1 AIC · ⊞ 17.8K ·

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

Labels

copilot-sdk-auto-upgrade Automated Copilot SDK/CLI version-bump PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants