Skip to content

chore: bump @github/copilot-sdk to 1.0.12-preview.0 and @github/copilot to 1.0.81-5 - #331776

Closed
vs-code-engineering[bot] wants to merge 4 commits into
mainfrom
automation/bump-copilot-sdk-1.0.12-preview.0-cli-1.0.81-5
Closed

chore: bump @github/copilot-sdk to 1.0.12-preview.0 and @github/copilot to 1.0.81-5#331776
vs-code-engineering[bot] wants to merge 4 commits into
mainfrom
automation/bump-copilot-sdk-1.0.12-preview.0-cli-1.0.81-5

Conversation

@vs-code-engineering

@vs-code-engineering vs-code-engineering Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

🤖 sdk-vscode-bump-fix — cycle 1

Root cause (Compile failure): SDK 1.0.12-preview.0 intentionally 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:

  • PermissionAllowAllModePermissionMode; values 'on'|'auto'|'off''allow-all'|'assisted'|'manual'
  • permissions.setAllowAll({mode}) RPC → permissions.setMode({mode}) (result {success, mode})
  • PermissionAutoApprovalPermissionAssistedApproval
  • promptRequest.autoApprovalpromptRequest.assistedApproval
  • Added new permission kind extension-env-access to the permissionKind union

Files: 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 string permissions.setMode, assistedApproval fixtures).

Local validation: Scoped typecheck of vs/platform/agentHost/** — all permission-API errors resolved. Remaining diagnostics in the scoped run (.css side-effect imports, Timeout, @vscode/copilot-api CCAModel/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 the x86_64 and aarch64 entries of referenceGeneratedDepsByArch in build/linux/rpm/dep-lists.ts.

Driven by (authoritative): Product build 466218 failed Prepare rpm package on Linux (X64) and Linux (ARM64) with Error: The dependencies list has changed. (from build/linux/dependencies-generator.ts). Diffing the build's Old vs New requires shows the sole change on both arches is the removal of libm.so.6(GLIBC_2.27)(64bit) — the bumped @github/copilot 1.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 + cli 1.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/copilot maintenance pins left frozen.

⚠️ Build-path edit — authorization required: The change is under 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.ts to the renamed SDK contract (offmanual, onallow-all, autoassisted), including the two sdkMode=... log-string assertions and the rejected permission mode message.

Verdict/insight driving it: Authoritative product build 466302 failed only in Run unit tests (Electron) across macOS/Linux/Windows with permissionModes deep-equal mismatches (actual manual/allow-all/assisted vs expected off/on/auto). Prior commit ce9518d migrated 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 for sdk=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 installed 1.0.12-preview.0 types. No koffi/glibc/signing surface involved.

Compatibility: SDK 1.0.12-preview.0 + CLI 1.0.81-5 pins 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-client was 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 failed tasks are Install dependencies (Linux X64 + ARM64), which failed in the foundry-local-sdk@1.2.3 postinstall:

npm error path .../node_modules/foundry-local-sdk
npm error command sh -c node script/install-standard.cjs
npm error [foundry-local] Installation failed: Failed to download Microsoft.AI.Foundry.Local.Core 1.2.3
  from any configured feed (api.nuget.org, pkgs.dev.azure.com): Download failed with status 401:
  (pkgs.dev.azure.com/redacted)

The ENOTEMPTY ... windows-foreground-love line 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, ...) is canceled — the standard cascade once the install job fails.

Why this is not the bump: foundry-local-sdk is pinned to 1.2.3 identically on main and this branch does not touch it — the bump diff is @github/copilot 1.0.81-0→1.0.81-5 and @github/copilot-sdk 1.0.11→1.0.12-preview.0 only, and the regenerated lockfiles contain no non-copilot package changes. The Microsoft.AI.Foundry.Local.Core NuGet 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/automanual/allow-all/assisted in copilotAgentSession.ts + agentHost tests, and the rpm dep-list refresh); those remain valid and were not re-touched.

Compatibility: SDK 1.0.12-preview.0 + CLI 1.0.81-5 pins 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 for Microsoft.AI.Foundry.Local.Core is 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 ·

Copilot AI balanced review requested due to automatic review settings August 20, 2026 11:11
@vs-code-engineering vs-code-engineering Bot added the copilot-sdk-auto-upgrade Automated Copilot SDK/CLI version-bump PR label Aug 20, 2026
@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

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

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

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/copilot from 1.0.81-0 to 1.0.81-5
  • Update @github/copilot-sdk from 1.0.11 to 1.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.

Comment thread package.json
"@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",
@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

Product build against the PR branch — cycle 1: failed

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>
@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

Commit pushed: ce9518d

Generated by sdk-vscode-bump-fix · opus48 · 491.5 AIC · ⌖ 27.2 AIC · ⊞ 18K

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

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

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

Product build against the PR branch — cycle 2: failed

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>
@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

Commit pushed: 33d3bfc

Generated by sdk-vscode-bump-fix · opus48 · 308.9 AIC · ⌖ 23.3 AIC · ⊞ 18K

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

⏸️ 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 33d3bfcbfd4dbc85db56299d97a86d4e1aa9d708 without advancing the iteration:

/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

Changed build/packaging files:

build/linux/rpm/dep-lists.ts

Inspection run: https://github.com/microsoft/vscode-engineering/actions/runs/32382267322

@pwang347

Copy link
Copy Markdown
Member

/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

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

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

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

Product build against the PR branch — cycle 3: failed

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>
@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

Commit pushed: 34f7d02

Generated by sdk-vscode-bump-fix · opus48 · 180 AIC · ⌖ 25 AIC · ⊞ 18K

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

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

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

Product build against the PR branch — cycle 4: failed

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

⚠️ Product build 466341 failed on an infra/feed issue, not the bump

Completed automated work (prior cycles): the actual Copilot SDK/CLI integration for sdk=1.0.12-preview.0 | cli=1.0.81-5 is already in this branch — the renamed permission-mode API migration (off/on/automanual/allow-all/assisted) in copilotAgentSession.ts and the agentHost tests, plus the rpm dep-list refresh. Nothing further was needed this cycle.

Why the build is red (not fixable in this PR): the only genuinely failed tasks are Install dependencies (Linux X64 + ARM64), failing in the foundry-local-sdk@1.2.3 postinstall:

[foundry-local] Installation failed: Failed to download Microsoft.AI.Foundry.Local.Core 1.2.3 ... Download failed with status 401 (internal NuGet feed pkgs.dev.azure.com/aiinfra)

foundry-local-sdk is pinned to 1.2.3 identically on main, is untouched by this bump, and the regenerated lockfiles contain no non-@github/copilot* changes. All other failing tasks are canceled cascades from that install failure. This is a feed-auth/infrastructure problem independent of the Copilot pins — no code change on this PR can resolve a feed-side 401.

Remaining human task: please re-run the product build for this PR head (34f7d02) once the internal Microsoft.AI.Foundry.Local.Core NuGet feed auth is healthy. I made no edits this cycle, so no build was auto-re-dispatched.

cc @pwang347 @anthonykim1

Generated by sdk-vscode-bump-fix · opus48 · 158.1 AIC · ⌖ 11.3 AIC · ⊞ 18K ·

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM! Code changes are clean and well-structured.

@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

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.yml. Reopen it if this bump is still wanted.

@vs-code-engineering
vs-code-engineering Bot deleted the automation/bump-copilot-sdk-1.0.12-preview.0-cli-1.0.81-5 branch August 27, 2026 14:40
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.

4 participants