chore: bump @github/copilot to 1.0.75#327464
Conversation
vs-code-engineering
Bot
added
the
copilot-sdk-auto-upgrade
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.
Updates the @github/copilot dependency to a newer patch version across the repo to keep Copilot components aligned.
Changes:
- Bumped
@github/copilotfrom^1.0.73to^1.0.75in the rootpackage.json - Bumped
@github/copilotfrom^1.0.73to^1.0.75inremote/package.json - Bumped
@github/copilotfrom^1.0.73to^1.0.75inextensions/copilot/package.json
Reviewed changes
Copilot reviewed 3 out of 6 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| remote/package.json | Updates @github/copilot dependency version to ^1.0.75. |
| package.json | Updates @github/copilot dependency version to ^1.0.75. |
| extensions/copilot/package.json | Updates @github/copilot dependency version to ^1.0.75. |
Files not reviewed (2)
- extensions/copilot/package-lock.json: Generated file
- remote/package-lock.json: Generated file
|
🏗️ Product build queued for cycle 1: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=458785 — validating the PR branch… |
|
❌ Product build against the PR branch — cycle 1:
|
|
Automated signed Copilot dependency bump.
@github/copilot:^1.0.73→^1.0.75main@dd862885ff5fbd279747c793e18105e6b7ddc805Draft 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.75No published path changes.
@github/copilot-darwin-x641.0.73 → 1.0.75No published path changes.
@github/copilot-linux-x641.0.73 → 1.0.75No published path changes.
@github/copilot-win32-x641.0.73 → 1.0.75No published path changes.
🤖 sdk-bump-fix status — cycle 1
Product build: ❌ failed (build 458785) —
@github/copilot-sdk@1.0.8·@github/copilot@1.0.75Integration changes pushed this cycle: none — blocked on upstream SDK, see below.
Root cause (classification: waiting on upstream SDK work/publication)
This is a CLI-only bump (
@github/copilot1.0.73 → 1.0.75); the SDK stays at@github/copilot-sdk@1.0.8. The authoritative product build fails at the Typecheck task, which cascades into the separate Copilot VSIX job failing (Copilot job status: result=failed) and therefore every downstreamDownload Copilot VSIX/ artifact / codesign / crash-report task. The published-package layout diff shows no path changes, so this is a type/contract-only change in the CLI's@github/copilot/sdksurface — exactly the kind of break that requires the matching SDK.SDK ↔ CLI correlation
1.0.8declares CLI range^1.0.73(CLI floor 1.0.73) — it was built/tested against CLI 1.0.73, not 1.0.75.^1.0.75. Published SDKs are only1.0.8(^1.0.73) and1.0.8-preview.0(^1.0.72).1.0.9(canary only, unpublished), and its SDK canary run 30082551267 FAILED on all three platforms (E2E ubuntu/macos/windows all failure), runtime1.0.75-canary.20.ged264c5.update-copilot/dependency-update PR exists for CLI 1.0.75.[sdk=1.0.9-canary.25.g949de90|cli=1.0.75-canary.20.ged264c5]uses SDK 1.0.9, not this PR's SDK 1.0.8 — so it is a non-matching-SDK hypothesis, but it corroborates that CLI 1.0.75 needs SDK 1.0.9-level changes that are not yet published or green. The last green canary was[sdk=1.0.8-canary.22|cli=1.0.74-canary.17]— an older CLI.Why no VS Code edit was made
Per the CLI-only-bump policy, when the CLI needs a newer SDK that is not yet published (and whose canary is failing, with no dependency-update PR landed), the correct action is not to patch VS Code call sites or edit version pins/lockfiles, but to escalate so a human can re-run this as a combined SDK+CLI bump once a compatible SDK (≈
1.0.9, declaring CLI^1.0.75) is published and green. Making speculative type edits here would mask the real upstream incompatibility.Smallest unresolved human task
Hold this PR (keep draft). Re-issue as a combined
@github/copilot-sdk+@github/copilotbump to a published SDK that declares CLI^1.0.75(expected1.0.9) once upstream publishes it and its SDK canary is green — or land the upstream SDK dependency-update first. No further automated cycles will help until then.