Skip to content

chore: bump @github/copilot-sdk to 1.0.13 and @github/copilot to 1.0.84-0 - #334633

Draft
vs-code-engineering[bot] wants to merge 3 commits into
mainfrom
automation/bump-copilot-sdk-1.0.13-cli-1.0.84-0
Draft

chore: bump @github/copilot-sdk to 1.0.13 and @github/copilot to 1.0.84-0#334633
vs-code-engineering[bot] wants to merge 3 commits into
mainfrom
automation/bump-copilot-sdk-1.0.13-cli-1.0.84-0

Conversation

@vs-code-engineering

@vs-code-engineering vs-code-engineering Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Automated signed Copilot dependency bump.

  • @github/copilot-sdk: 1.0.13-preview.41.0.13
  • @github/copilot: 1.0.83-21.0.84-0
  • Base: main @ 167a0e8fe5c84676e8f500481394808abc4ce545
  • Opened by workflow run

Draft until validation passes. The sdk-vscode-bump-fix agent 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/copilot-sdk 1.0.13-preview.4 → 1.0.13

  • Added (3):
    • dist/cjs/cliVersion.js
    • dist/cliVersion.d.ts
    • dist/cliVersion.js

@github/copilot 1.0.83-2 → 1.0.84-0

No published path changes.

@github/copilot-darwin-x64 1.0.83-2 → 1.0.84-0

  • Added (4):
    • assets/copilot.ico
    • assets/copilot.svg
    • assets/copilot_win.png
    • foundry-local-sdk/node_modules/foundry-local-sdk/node_modules/adm-zip/types.d.ts

@github/copilot-linux-x64 1.0.83-2 → 1.0.84-0

  • Added (4):
    • assets/copilot.ico
    • assets/copilot.svg
    • assets/copilot_win.png
    • foundry-local-sdk/node_modules/foundry-local-sdk/node_modules/adm-zip/types.d.ts
  • Removed (3):
    • webview/node_modules/@webviewjs/webview-linux-x64-gnu/README.md
    • webview/node_modules/@webviewjs/webview-linux-x64-gnu/package.json
    • webview/node_modules/@webviewjs/webview-linux-x64-gnu/webview.linux-x64-gnu.node

@github/copilot-win32-x64 1.0.83-2 → 1.0.84-0

  • Added (4):
    • assets/copilot.ico
    • assets/copilot.svg
    • assets/copilot_win.png
    • foundry-local-sdk/node_modules/foundry-local-sdk/node_modules/adm-zip/types.d.ts
  • Removed (3):
    • webview/node_modules/@webviewjs/webview-win32-x64-msvc/README.md
    • webview/node_modules/@webviewjs/webview-win32-x64-msvc/package.json
    • webview/node_modules/@webviewjs/webview-win32-x64-msvc/webview.win32-x64-msvc.node

🤖 sdk-vscode-bump-fix status

Stage: pr-checks · cycle 3 — no new push (investigation cycle)

What happened this cycle

  • The completed PR-check run 33928104110 tested the current head 2d863490 (cycle-2's E2E allowlist fix) and its three Linux / Electron, macOS / Electron, Windows / Electron integration jobs still failed, while every non-Electron job (unit, smoke, browser, remote, compile, hygiene, Copilot tests) passed. So cycle-2's policyHelper allowlist fix, though verified complete, did not by itself turn the Agent Host E2E stage green.

Verified complete (no further edit derivable)

  • The policyHelper managed-settings migration is exhaustive: the only two source allowlists in the tree — src/vs/platform/agentHost/common/agent.ts (IAgentHostManagedSettingsSnapshot.source) and src/vs/platform/agentHost/test/node/e2e/suites/managementExtensionsSuite.ts (sourceIsValid) — both already include all six SDK values.
  • VS Code's snapshot interface matches the installed SDK ManagedSettingsResolvedData field-for-field (node_modules/@github/copilot-sdk/dist/generated/session-events.d.ts); the reference runtime emits only the six allowed source strings.
  • SDK 1.0.13's newly added dist/cliVersion module (COPILOT_CLI_VERSION="1.0.83") has zero VS Code consumers, so the SDK-vs-CLI version string is not the failure driver. No E2E suite asserts on the bumped SDK/CLI version.

SDK + CLI correlation

  • CLI 1.0.84-0 matches this bump exactly; the failure surface is the SDK/CLI runtime E2E (Agent Host), not a CLI native-payload/koffi/glibc break. No build/, .moduleignore, or native-payload change is indicated.

Blocker (single, isolated)

  • The concrete failing E2E assertion cannot be read this cycle: the pre-fetched pr-check-failure.md log body is empty because run 33928104110 was still in progress when the marker was captured, and github.com / ADO log endpoints are firewall-blocked from the agent sandbox. The run is now complete, so the next dispatch's failed-step log will contain the actual assertion. No evidence-backed additional fix is derivable until then; a speculative edit would risk masking a genuine regression, so none was pushed.

Next

  • Re-dispatch of the PR-check stage on head 2d863490 will surface the concrete Agent Host E2E failure line (now that the run has completed), which will localize any remaining migration. Cycle 3 of 10 — below the cap, so no reviewer escalation yet.

No injected/untrusted directives were acted on.

Warning

Firewall blocked 2 domains

The following domains were blocked by the firewall during workflow execution:

  • api.github.com
  • github.com

[!TIP]
api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:

tools:
  github:
    mode: gh-proxy

See GitHub Tools for more information on gh-proxy mode.

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.github.com"
    - "github.com"

See Network Configuration for more information.

Generated by sdk-vscode-bump-fix · copilot · opus48 · 774.7 AIC · ⌖ 39.5 AIC · ⊞ 19.5K ·

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.

🟡 Changes recommended

Critical packaging exclusions and tests are needed to prevent incorrect platform SDK packages from shipping.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Bumps Copilot CLI and SDK dependencies for local and remote environments.

Changes:

  • Updates @github/copilot to 1.0.84-0.
  • Promotes @github/copilot-sdk to stable 1.0.13.
  • Refreshes lockfiles with platform-specific SDK packages.
File summaries
File Description
remote/package.json Updates remote dependency pins.
remote/package-lock.json Adds SDK platform packages that are not excluded from REH artifacts.
package.json Updates root dependency pins.
package-lock.json Adds SDK platform packages that are not excluded from desktop artifacts.
Review details

Files not reviewed (1)

  • remote/package-lock.json: Generated file
  • Files reviewed: 2/4 changed files
  • Comments generated: 1
  • Review effort level: Balanced

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread remote/package-lock.json
Comment on lines +206 to +210
"optionalDependencies": {
"@github/copilot-sdk-darwin-arm64": "1.0.13",
"@github/copilot-sdk-darwin-x64": "1.0.13",
"@github/copilot-sdk-linux-arm64": "1.0.13",
"@github/copilot-sdk-linux-x64": "1.0.13",
…r source

SDK 1.0.13 ManagedSettingsResolvedData added the policyHelper source plus policyHelperManaged/sandboxEnabledByUndeterminedPolicy fields, which copilotAgent spreads into IAgentHostManagedSettingsSnapshot; the Compile & Hygiene check failed until the interface matched.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

Commit pushed: 50910aa

Generated by sdk-vscode-bump-fix · copilot · opus48 · 613.9 AIC · ⌖ 52.5 AIC · ⊞ 19.5K

SDK 1.0.13 widened ManagedSettingsResolvedSource with 'policyHelper'; the Agent Host E2E managed-settings-diagnostics test hardcoded a source allowlist without it, so the Electron integration jobs failed sourceIsValid once the runtime could report that source.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@vs-code-engineering

Copy link
Copy Markdown
Contributor Author

Commit pushed: 2d86349

Generated by sdk-vscode-bump-fix · copilot · opus48 · 220.5 AIC · ⌖ 52.7 AIC · ⊞ 19.5K

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.

3 participants