chore: bump @github/copilot-sdk to 1.0.12-preview.0 and @github/copilot to 1.0.81-5 - #331776
chore: bump @github/copilot-sdk to 1.0.12-preview.0 and @github/copilot to 1.0.81-5#331776vs-code-engineering[bot] wants to merge 4 commits into
Conversation
|
🏗️ Product build queued for cycle 1: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=466210 — validating the PR branch… |
There was a problem hiding this comment.
Pull request overview
Warning
Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.
Bumps pinned Copilot dependencies to newer versions across the root and remote/ packages.
Changes:
- Update
@github/copilotfrom1.0.81-0to1.0.81-5 - Update
@github/copilot-sdkfrom1.0.11to1.0.12-preview.0
Reviewed changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Updates pinned Copilot and Copilot SDK dependency versions in the root package. |
| remote/package.json | Mirrors the same Copilot and Copilot SDK dependency bumps for the remote package. |
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.
| "@github/copilot": "1.0.81-0", | ||
| "@github/copilot-sdk": "1.0.11", | ||
| "@github/copilot": "1.0.81-5", | ||
| "@github/copilot-sdk": "1.0.12-preview.0", |
|
❌ Product build against the PR branch — cycle 1:
|
SDK 1.0.12-preview.0 renamed the permission contract: PermissionAllowAllMode
-> PermissionMode ('on'|'auto'|'off' -> 'allow-all'|'assisted'|'manual'),
permissions.setAllowAll -> setMode, PermissionAutoApproval ->
PermissionAssistedApproval, and promptRequest.autoApproval ->
assistedApproval. Adds the new 'extension-env-access' permission kind.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Commit pushed:
|
|
🏗️ Product build queued for cycle 2: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=466218 — validating the PR branch… |
|
❌ Product build against the PR branch — cycle 2:
|
Product build 466218 failed 'Prepare rpm package' (Linux X64+ARM64): the generated rpm requires no longer include libm.so.6(GLIBC_2.27)(64bit) after the @github/copilot 1.0.81-5 / sdk 1.0.12-preview.0 bump lowered its libm glibc baseline. Drop that symbol from both x86_64 and aarch64 referenceGeneratedDepsByArch so the expected list matches. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Commit pushed:
|
|
⏸️ Product build stopped before queueing. This PR changes build/packaging files that the product pipeline executes with production credentials. A repository collaborator must review the changes, then comment this exact command on the PR to authorize a build of commit
Changed build/packaging files: Inspection run: https://github.com/microsoft/vscode-engineering/actions/runs/32382267322 |
|
/sdk-bump-approve-build cycle=3 head=33d3bfcbfd4dbc85db56299d97a86d4e1aa9d708 branch=automation/bump-copilot-sdk-1.0.12-preview.0-cli-1.0.81-5 sdk=1.0.12-preview.0 cli=1.0.81-5 retry=0 base=ce9518db6c88fca5230f242020548d002081a96b |
|
🏗️ Product build queued for cycle 3: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=466302 — validating the PR branch… |
|
❌ Product build against the PR branch — cycle 3:
|
SDK 1.0.12-preview.0 renamed permission modes (off/on/auto -> manual/allow-all/assisted); the prior migration updated production code but left copilotAgentSession.test.ts asserting the old literals, failing the Electron unit tests in build 466302. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Commit pushed:
|
|
🏗️ Product build queued for cycle 4: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=466341 — validating the PR branch… |
|
❌ Product build against the PR branch — cycle 4:
|
|
Mohammad javad Dianat (dianatofficial)
left a comment
There was a problem hiding this comment.
LGTM! Code changes are clean and well-structured.
|
Closing this automated Copilot SDK/CLI bump PR: it has been open for more than a week and newer signed versions have since been targeted by |
🤖 sdk-vscode-bump-fix — cycle 1
Root cause (Compile failure): SDK
1.0.12-preview.0intentionally renamed the permission contract. VS Code's agentHost Copilot integration still used the old names, producing the TS2305/TS2724/TS2339/TS2322/TS2353 errors in the product build.SDK+CLI correlation: This is the exact signed pair for this PR (
sdk=1.0.12-preview.0 | cli=1.0.81-5) — the authoritative product-build digest reports these compile errors directly, so no canary/CLI-mismatch caveat applies. Intentional API rename → VS Code adaptation (not a regression to mask).Contract migration applied:
PermissionAllowAllMode→PermissionMode; values'on'|'auto'|'off'→'allow-all'|'assisted'|'manual'permissions.setAllowAll({mode})RPC →permissions.setMode({mode})(result{success, mode})PermissionAutoApproval→PermissionAssistedApprovalpromptRequest.autoApproval→promptRequest.assistedApprovalextension-env-accessto thepermissionKindunionFiles:
common/agent.ts,node/copilot/copilotAgentSession.ts,test/node/copilotAgent.test.ts,test/node/copilotAgentSession.test.ts(both test mocks + fixtures migrated:setMode, op-log stringpermissions.setMode,assistedApprovalfixtures).Local validation: Scoped typecheck of
vs/platform/agentHost/**— all permission-API errors resolved. Remaining diagnostics in the scoped run (.cssside-effect imports,Timeout,@vscode/copilot-apiCCAModel/RequestType) are pre-existing, unrelated to this change, and only surface because the ambient/full build graph isn't loaded by the narrowed project (full-project tsc OOMs on this 8 GB runner). Pushed for the product build to validate the native/full surface.Next: awaiting product build for this branch.> Generated by sdk-vscode-bump-fix · opus48 · 491.5 AIC · ⌖ 27.2 AIC · ⊞ 18K · ◷
🤖 sdk-vscode-bump-fix — cycle 2
What changed this cycle: Removed
libm.so.6(GLIBC_2.27)(64bit)from both thex86_64andaarch64entries ofreferenceGeneratedDepsByArchinbuild/linux/rpm/dep-lists.ts.Driven by (authoritative): Product build 466218 failed
Prepare rpm packageon Linux (X64) and Linux (ARM64) withError: The dependencies list has changed.(frombuild/linux/dependencies-generator.ts). Diffing the build's Old vs New requires shows the sole change on both arches is the removal oflibm.so.6(GLIBC_2.27)(64bit)— the bumped@github/copilot1.0.81-5 native payload no longer links a libm symbol versioned at GLIBC 2.27, lowering its libm baseline. The reference list is updated to match the newly generated requires.SDK+CLI correlation: Fix is driven purely by the exact signed pair product build (sdk
1.0.12-preview.0+ cli1.0.81-5). The Slack canary threads are on a different CLI (1.0.81-canary.*, unsigned) and contained no suggested action, so they were treated as non-authoritative and not adopted. No runtime/smoke logs were captured (rpm packaging failure, not a smoke job) — expected.Compatibility: Signed-pair bump; native-payload glibc-baseline drift only. No API/type/protocol change implicated by this failure; no version pins or lockfiles touched.
extensions/copilotmaintenance pins left frozen.build/, so validation stops before queueing until a trusted collaborator authorizes this exact PR head. The edit is minimal and self-evidently scoped: two deleted lines removing one obsolete symbol from a reference list, justified directly by the build's own Old/New requires diff (not by any comment/Slack suggestion).Build state: Awaiting re-dispatched product build after authorization. No other integration changes appear required by build 466218.> Generated by sdk-vscode-bump-fix · opus48 · 308.9 AIC · ⌖ 23.3 AIC · ⊞ 18K · ◷
🤖 SDK bump fixer — cycle 3
Change this cycle: Migrated the remaining permission-mode expectations in
src/vs/platform/agentHost/test/node/copilotAgentSession.test.tsto the renamed SDK contract (off→manual,on→allow-all,auto→assisted), including the twosdkMode=...log-string assertions and therejected permission modemessage.Verdict/insight driving it: Authoritative product build 466302 failed only in Run unit tests (Electron) across macOS/Linux/Windows with
permissionModesdeep-equal mismatches (actualmanual/allow-all/assistedvs expectedoff/on/auto). Prior commitce9518dmigrated production code (copilotAgentSession.ts) but left these test expectations on the old literals.SDK+CLI correlation: This is a pure API/type migration owned by VS Code, not a native-payload/CLI issue — so the CLI (
1.0.81-5) match is not decisive here. The canary threads forsdk=1.0.12-canary.*|cli=1.0.81-canary.*share this SDK base; the failing member is the renamed permission enum, which is present in the installed1.0.12-preview.0types. No koffi/glibc/signing surface involved.Compatibility: SDK
1.0.12-preview.0+ CLI1.0.81-5pins unchanged; no lockfile/pin edits. No build/packaging paths touched.Remaining human task: None identified — awaiting the re-dispatched product build to confirm green. Note: local
npm run typecheck-clientwas OOM-killed in the sandbox, but the edits are string-literal-only and mirror the already-migrated production contract.Product-build state: Fix pushed; product build re-dispatches automatically.> Generated by sdk-vscode-bump-fix · opus48 · 180 AIC · ⌖ 25 AIC · ⊞ 18K · ◷
🤖 SDK bump fixer — cycle 4
Change this cycle: None. No integration edits — the failing product build (466341) did not fail on anything the Copilot SDK/CLI bump owns.
Root cause (build 466341): The only genuinely
failedtasks are Install dependencies (Linux X64 + ARM64), which failed in thefoundry-local-sdk@1.2.3postinstall:The
ENOTEMPTY ... windows-foreground-loveline is just npm's rollback cleanup warning after that failure, not the cause. Every other reported task (Codesign, Agent SDK build+upload, Notarize, Compile, Build server, simulation tests, ...) iscanceled— the standard cascade once the install job fails.Why this is not the bump:
foundry-local-sdkis pinned to1.2.3identically onmainand this branch does not touch it — the bump diff is@github/copilot 1.0.81-0→1.0.81-5and@github/copilot-sdk 1.0.11→1.0.12-preview.0only, and the regenerated lockfiles contain no non-copilotpackage changes. TheMicrosoft.AI.Foundry.Local.CoreNuGet feed download returns 401 (auth), an internal-feed/infrastructure failure that reproduces regardless of the Copilot pins.SDK+CLI correlation: N/A for this failure — no koffi/glibc/native-payload/signing/type/protocol surface is implicated. The prior cycles already completed the real integration work for this pair (renamed permission-mode API
off/on/auto→manual/allow-all/assistedincopilotAgentSession.ts+ agentHost tests, and the rpm dep-list refresh); those remain valid and were not re-touched.Compatibility: SDK
1.0.12-preview.0+ CLI1.0.81-5pins unchanged; no lockfile/pin/build/packaging edits this cycle.Remaining human task: Re-run the product build for this PR head (
34f7d02) once the internal NuGet feed auth forMicrosoft.AI.Foundry.Local.Coreis healthy. No code change on this PR can fix a feed-side 401; nothing was pushed, so no build was auto-re-dispatched.Product-build state: Red on build 466341 due to the feed-auth/infra failure above — not blocked on integration work.> Generated by sdk-vscode-bump-fix · opus48 · 158.1 AIC · ⌖ 11.3 AIC · ⊞ 18K · ◷