chore: bump @github/copilot to 1.0.83-2 - #333970
Conversation
There was a problem hiding this comment.
🔵 Needs a closer look
The bundled cross-platform executable dependency requires the pending authoritative product validation.
Pull request overview
Updates the bundled GitHub Copilot dependency from 1.0.83-0 to 1.0.83-2 across desktop and remote environments.
Changes:
- Updates both dependency manifests.
- Regenerates lockfile versions, platform packages, URLs, and integrity hashes.
File summaries
| File | Description |
|---|---|
package.json |
Updates the root dependency pin. |
package-lock.json |
Locks updated desktop packages and binaries. |
remote/package.json |
Updates the remote dependency pin. |
remote/package-lock.json |
Locks updated remote packages and binaries. |
Review details
Files not reviewed (1)
- remote/package-lock.json: Generated file
- Files reviewed: 2/4 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
🏗️ Full product build queued for cycle 1: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=470206 — validating the PR branch… |
|
❌ Full product build against the PR branch — cycle 1:
|
The prior product build (470206) failed only on the macOS CLI (ARM64) Rust compile+notarize job, which is structurally independent of the @github/copilot npm bump (the CLI pipeline references no copilot packages) and is flagged in-pipeline as a known build flake (todo@connor4312, MSRUSTUP_LOG=debug). All other CLI-arch jobs passed; every other job cascade-cancelled. No VS Code integration change is warranted; re-run the authoritative product build. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
🏗️ Full product build queued for cycle 2: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=470219 — validating the PR branch… |
|
✅ Full product build against the PR branch — cycle 2:
|
Automated signed Copilot dependency bump.
@github/copilot:1.0.83-0→1.0.83-2main@1b7f001f6cf1cae59263ff33debf84cbb3e6af1fDraft until validation passes. The
sdk-vscode-bump-fixagent first iterates on Linux PR checks (up to 10 cycles), then on the authoritative full product build (up to 5 cycles).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.83-0 → 1.0.83-2No published path changes.
@github/copilot-darwin-x641.0.83-0 → 1.0.83-2builtin-skills/discover-resources/SKILL.mdbuiltin/discover-resources/SKILL.mdcopilot-sdk/runtimeArtifacts.d.ts@github/copilot-linux-x641.0.83-0 → 1.0.83-2builtin-skills/discover-resources/SKILL.mdbuiltin/discover-resources/SKILL.mdcopilot-sdk/runtimeArtifacts.d.ts@github/copilot-win32-x641.0.83-0 → 1.0.83-2builtin-skills/discover-resources/SKILL.mdbuiltin/discover-resources/SKILL.mdcopilot-sdk/runtimeArtifacts.d.ts🔧 sdk-vscode-bump-fix — product build, cycle 1
Verdict: No VS Code integration change warranted — re-triggered the authoritative product build.
Root cause of build 470206 failure: The only job with a genuine
failureconclusion was⭐️ VS Code (macOS macOS CLI (ARM64))(terminal at 11:37:13, the earliest to finish and the cascade trigger). Every other product-build job is a downstreamcancelled(cascade), not an independent failure. That macOS CLI job builds the RustcodeCLI and runs ESRP codesign/notarize; it does not consume the@github/copilotnpm packages this bump touches (nocopilotreferences anywhere inbuild/azure-pipelines/cli/**orproduct-build-darwin-cli.yml), and the pipeline itself flags it as a known build-flake surface (# todo@connor4312 to diagnose build flakes,MSRUSTUP_LOG: debug). All the other CLI-arch jobs — Linux x64/arm64/armhf, Alpine x64/arm64 — succeeded on this exact branch.SDK+CLI correlation / compatibility: This is a CLI-only patch bump
@github/copilot 1.0.83-0 → 1.0.83-2(SDK@github/copilot-sdk 1.0.13-preview.4unchanged). SDK compatibility is confirmed fine: SDK1.0.13-preview.4declares CLI floor^1.0.83-0(covers1.0.83-2), the exact-match SDK canary is green across macOS/ubuntu/windows, and the public npm publish succeeded. No upstream SDK bump is pending or required. The Slack canary threads reference1.0.83-canary.*builds (a different CLI than1.0.83-2) — treated as non-authoritative hypotheses only.Evidence that no integration edit is needed:
1.0.83-0 → 1.0.83-2) is purely additive:builtin-skills/discover-resources/SKILL.md,builtin/discover-resources/SKILL.md,copilot-sdk/runtimeArtifacts.d.ts. No native binary added, removed, or renamed.copilotCLISDKUpgrade.spec.ts) passes against the installed1.0.83-2package, and the SDK loads without error.extensions/copilottypecheck is clean; no API/type migration surfaced.1.0.83version references outside the lockfiles.Action: Pushed an empty commit to re-run the product build. If the re-run reproduces a macOS CLI (ARM64)-only failure, that is a CLI/infra build flake to escalate to the pipeline owner, not a bump-integration defect.
Stage: product build, cycle 1 of 5 — validation re-queued.> Generated by sdk-vscode-bump-fix · opus48 · 470.8 AIC · ⌖ 23 AIC · ⊞ 18.3K · ◷