Skip to content

Update Copilot CLI to 1.0.86-0 - #2694

Merged
stephentoub merged 6 commits into
mainfrom
update-copilot-1.0.86-0
Sep 16, 2026
Merged

stephentoub merged 6 commits into
mainfrom
update-copilot-1.0.86-0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated update of the Copilot CLI release to version 1.0.86-0.

Changes

  • Updated the shared release pin in nodejs/package.json
  • Validated the release assets listed in SHA256SUMS.txt
  • Re-ran all code generators (scripts/codegen)
  • Formatted generated output
  • Regenerated Java types from the pinned CLI release schemas

Java Handwritten Code Adaptation Plan

If java-sdk-tests CI fails on this PR, follow these steps:

  1. Identify failures: Run mvn clean, mvn verify from java/ locally or check the java-sdk-tests workflow run logs.
  2. Categorize errors:
    • Constructor signature changes (new fields added to generated records)
    • Enum value additions/renames in generated types
    • New event types requiring handler registration
    • Removed or renamed generated types
  3. Fix handwritten source (java/sdk/src/main/java/com/github/copilot/sdk/):
    • Update call sites passing positional constructor args to include new fields (typically null for optional new fields).
    • Update switch/if-else over enum values to handle new cases.
    • Register handlers for new event types in CopilotSession.java if applicable.
  4. Fix handwritten tests (java/sdk/src/test/java/com/github/copilot/sdk/):
    • Same constructor/enum fixes as above.
    • Add new test methods for new functionality if the change adds user-facing API surface.
  5. Validate: cd java && mvn clean test-compile jar:jar && mvn verify -Dskip.test.harness=true
  6. Format: cd java && mvn spotless:apply
  7. Push fixes to this PR branch.

To automate this, trigger the java-adapt-handwritten-code-to-accept-upgrade-changes agentic workflow instead.

Next steps

When ready, click Ready for review to trigger CI checks.

Created by the Update Copilot CLI Version workflow.

- Updated the shared CLI release pin
- Re-ran code generators
- Formatted generated code
@stephentoub
stephentoub marked this pull request as ready for review September 16, 2026 13:59
@stephentoub
stephentoub requested a review from a team as a code owner September 16, 2026 13:59
Copilot AI balanced review requested due to automatic review settings September 16, 2026 13:59

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.

🟢 Approval recommended

The release and required assets exist, and both version pins are consistent.

Pull request overview

Updates the SDK’s shared Copilot CLI pin to 1.0.86-0.

Changes:

  • Updated package metadata and generated runtime version constant.
  • Kept both version sources synchronized.
File summaries
File Description
nodejs/package.json Updates the shared CLI release pin.
nodejs/src/cliVersion.ts Updates compiled CLI version metadata.
Review details
  • Files reviewed: 2/2 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.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

Isolate the remaining auto-tier subtests and rearm Unix signal handlers after FFI connection initialization.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@github-actions

This comment has been minimized.

Repair foreign signal handlers before runtime and harness child-process teardown so Go retains SA_ONSTACK across embedded libuv lifecycle changes.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@github-actions

This comment has been minimized.

@stephentoub
stephentoub added this pull request to the merge queue Sep 16, 2026
Correct the Go FFI mitigation comments to identify Tokio signal-hook-registry rather than libuv as the component dropping SA_ONSTACK.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@stephentoub
stephentoub removed this pull request from the merge queue due to a manual request Sep 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor Author

SDK Consistency Review

Reviewed the full PR delta (get_files + get_diff for PR #2694).

Changes in this PR:

  1. CLI version pin bump (1.0.851.0.86-0) in nodejs/package.json and nodejs/src/cliVersion.ts. This is the single source of truth for the pinned CLI release — Rust (rust/build/in_process.rs, rust/build/out_of_process.res), Python (python/e2e/conftest.py), and the Go bundler (go/cmd/bundler/main.go) all read copilotCliVersion from nodejs/package.json rather than duplicating the value, so no other SDK files need updating for this change. ✅ Consistent.
  2. Go-only FFI signal-handling fix (go/internal/ffihost/*, go/internal/e2e/testharness/*, e2e test guards): repairs SA_ONSTACK on the SIGCHLD handler that Tokio's signal-hook-registry installs, since the Go runtime specifically aborts when a non-Go handler lacks SA_ONSTACK. This is a Go-runtime-specific constraint (documented in the updated comments in sigonstack_darwin.go/sigonstack_linux.go) — other embedded-runtime hosts (Rust in_process.rs, .NET InProcessEnvIsolation.cs, Java InProcessRuntimeConnection.java, Node's in-process FFI tests, Python's in-process e2e tests) don't share Go's signal-handler-flag requirement, so there's no equivalent fix needed in those SDKs for this particular issue.

Conclusion: No cross-SDK consistency issues found. The version bump follows the established single-source-of-truth pattern, and the FFI signal-handling fix addresses a Go-runtime-specific quirk that has no direct analogue in the other language implementations. No inline review comments needed.

Generated by SDK Consistency Review Agent for #2694 · copilot · sonnet50 · 24.6 AIC · ⌖ 12.2 AIC · ⊞ 8.3K ·

@stephentoub
stephentoub added this pull request to the merge queue Sep 16, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Sep 16, 2026
@stephentoub
stephentoub added this pull request to the merge queue Sep 16, 2026
Merged via the queue into main with commit 7dc8827 Sep 16, 2026
108 checks passed
@stephentoub
stephentoub deleted the update-copilot-1.0.86-0 branch September 16, 2026 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants