chore: bump @github/copilot to 1.0.79 - #330228
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 use the stable 1.0.79 release instead of the 1.0.79-9 pre-release build.
Changes:
- Bump
@github/copilotfrom1.0.79-9to1.0.79in the rootpackage.json - Bump
@github/copilotfrom1.0.79-9to1.0.79inremote/package.json
Reviewed changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Switch @github/copilot dependency from pre-release to stable version |
| remote/package.json | Keep remote package aligned by switching @github/copilot to stable version |
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.
| "dependencies": { | ||
| "@anthropic-ai/sdk": "^0.82.0", | ||
| "@github/copilot": "1.0.79-9", | ||
| "@github/copilot": "1.0.79", |
|
🏗️ Product build queued for cycle 1: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=463613 — validating the PR branch… |
|
✅ Product build against the PR branch — cycle 1:
|
|
🏗️ Product build queued for cycle 1: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=464009 — validating the PR branch… |
|
❌ Product build against the PR branch — cycle 1:
|
Automated signed Copilot dependency bump.
@github/copilot:1.0.79-9→1.0.79main@e85b5d14ba55c440f9053679040edfe880b705d4Draft 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.79-9 → 1.0.79No published path changes.
@github/copilot-darwin-x641.0.79-9 → 1.0.79No published path changes.
@github/copilot-linux-x641.0.79-9 → 1.0.79No published path changes.
@github/copilot-win32-x641.0.79-9 → 1.0.79No published path changes.
🤖 sdk-vscode-bump-fix status — cycle 1
No integration changes needed. The failing product build (464009) reports a single failing task, and it is not an SDK/CLI integration failure.
Authoritative failure (build 464009):
succeededWithIssues. The OSPO NOTICE File Generator service returnedfailed to call notice file generator API/Generation failedon all 3 retries and thenThe task has timed out.Classification: Infrastructure failure (Component Governance / OSPO notice-generation API), not a package-contract problem.
package.json+package-lock.json(root andremote/); pins are correct:@github/copilot@1.0.79,@github/copilot-sdk@1.0.10-preview.0.extensions/copilotleft frozen.logs-*-smoke-*artifact — the failure is not in a test job). The failing task sits in Quality Checks, far from install/compile/packaging/signing/native-payload surfaces.@github/copilotor any per-arch package, so no packaging/pruning (.vscodeignore,build/.moduleignore,build/lib/copilot.ts) adaptation is implied.SDK+CLI correlation & compatibility:
1.0.10-preview.0, which declares CLI range^1.0.79-6(floor1.0.79-6) — this covers the bump's CLI1.0.79. The SDK dependency-update PR (Update @github/copilot to 1.0.79 github/copilot-sdk#2306) is merged. So the branch SDK properly supports CLI 1.0.79; no SDK bump required.1.0.80-canary.*) than this signed pair (1.0.79), so their failures are not correlated to this bump and were not adopted.Smallest unresolved human task: none actionable in VS Code. The ThirdPartyNotices/CG notice-generator API timeout is a transient external-service failure — re-dispatch the product build (or let CG retry). If it recurs across builds, it is an OSPO/CG service issue to escalate outside this integration, not a bump defect.
Product-build state: failing only on the CG notice-generation service timeout; no code pushed this cycle.