Skip to content

Update Copilot SDK to 1.0.26 - #266

Merged
SIkebe merged 1 commit into
mainfrom
sikebe-copilot-sdk-1-0-26
Oct 23, 2026
Merged

SIkebe merged 1 commit into
mainfrom
sikebe-copilot-sdk-1-0-26

Conversation

@SIkebe

@SIkebe SIkebe commented Oct 23, 2026

Copy link
Copy Markdown
Owner

Summary

Update GitHub.Copilot.SDK from 1.0.26-preview.0 to the stable 1.0.26 release. This aligns the bundled Copilot CLI runtime to 1.0.103, updates the displayed third-party notice, and keeps the in-process runtime version assertion in sync. The SDK release notes and v1.0.25-to-v1.0.26 source diff were reviewed; the app does not use the removed remote-session API, so no functional migration was needed. The SDK's FFI callback lifetime and request-correlated send/wait improvements are picked up automatically.

Related Issues

N/A - no issue to close.

Scope

  • App UI / workflow
  • Core services / data model
  • Copilot SDK / agent behavior
  • Preview / WebView2
  • Documentation / release readiness
  • Tests / tooling
  • Other:

Validation

  • dotnet build RepoSyncRadar.sln -warnaserror - passed (0 warnings, 0 errors)
  • dotnet test RepoSyncRadar.sln -- --filter-not-trait Category=Manual - executed with the skill-prescribed --timeout 10m before --; 1,579 passed and 2 failed. The failures were TcpPreviewPortAllocatorTests.AllocateSingle_Skips_Listening_Preferred_Port and AllocateComparison_Skips_Pair_When_After_Port_Is_Listening; both are unrelated port-allocation assertions. App.Tests (827), App.E2E.Tests (27), and Integrations.Tests (55) passed.
  • Focused tests: N/A - SDK/runtime and notice tests ran in the full solution test suite.
  • Manual smoke / screenshots, if UI or WebView behavior changed; otherwise replace with N/A - no UI/WebView changes: N/A - no UI/WebView changes

Risk And Rollback

  • User impact: Stable SDK and bundled runtime update; no app workflow changes.
  • Operational risk: Low. The in-process runtime bundle and reported runtime version were exercised by automated tests.
  • Rollback plan: Revert the package, notice, and runtime assertion version changes together.

Release Notes

  • User-facing change
  • Internal-only change
  • No release note needed

Release note draft:

Internal dependency update: GitHub.Copilot.SDK 1.0.26 with bundled Copilot CLI runtime 1.0.103.

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

Copilot-Session: 4b26ae75-045d-4c38-a1ae-81edaad4b947
Copilot AI balanced review requested due to automatic review settings October 23, 2026 00:29

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟢 Approval recommended

The four version changes are consistent, with no identified blocking issues or evidence linking the reported port-allocation failures to this update.

No open issues 🎉

What changed in this PR

Updates RepoSyncRadar’s Copilot integration from 1.0.26-preview.0 to stable 1.0.26, with no application workflow changes.

Changes:

  • Upgrades the centrally managed SDK dependency.
  • Synchronizes the third-party notice and its test with 1.0.26.
  • Updates the bundled runtime assertion to 1.0.103.

Reported validation includes a successful build and passing app, E2E, and integration tests; two port-allocation tests failed.

File Description
tests/​RepoSyncRadar.App.Tests/​Copilot/​CopilotInProcessRuntimeTests.cs Expects bundled runtime version 1.0.103.
tests/​RepoSyncRadar.App.Tests/​Components/​ThirdPartyNoticesPanelTests.cs Expects SDK notice version 1.0.26.
src/​RepoSyncRadar.App/​Settings/​ThirdPartyNotices.cs Displays the stable SDK version.
Directory.Packages.props Pins GitHub.Copilot.SDK to 1.0.26.

Review effort: Balanced

@SIkebe
SIkebe merged commit 1a9de13 into main Oct 23, 2026
10 checks passed
@SIkebe
SIkebe deleted the sikebe-copilot-sdk-1-0-26 branch October 23, 2026 00:43
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