Repository navigation
deps: roll GitHub.Copilot.SDK back to 1.0.11 - #1198
Merged
Alexandre Zollinger Chohfi (azchohfi) merged 1 commit intoSep 11, 2026
Merged
Alexandre Zollinger Chohfi (azchohfi) merged 1 commit into
Alexandre Zollinger Chohfi (azchohfi) merged 1 commit into
Conversation
1.0.13 is not available on the internal NuGet feed used by the OneBranch CI and release pipelines, which breaks restore on main. Pin back to 1.0.11, the last version present on that feed. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 41ba9db5-e3b7-422b-a379-7b0971e0d368
Alexandre Zollinger Chohfi (azchohfi)
requested a review
from Chris Anderson (codemonkeychris)
as a code owner
September 11, 2026 06:07
Alexandre Zollinger Chohfi (azchohfi)
deleted the
azchohfi-rollback-copilot-sdk-1-0-11
branch
September 11, 2026 06:09
This was referenced Sep 11, 2026
Alexandre Zollinger Chohfi (azchohfi)
added a commit
that referenced
this pull request
Sep 15, 2026
Applies the bumps from bot/windows-nuget-updates that are provably
resolvable from the internal Azure Artifacts feed, and holds back the
two that are not.
Microsoft.Data.Sqlite 11.0.0-preview.7.26381.103 -> 11.0.0-rc.1.26425.128
Microsoft.Extensions.Logging.Abstractions 10.0.11 -> 10.0.12
Microsoft.NET.Test.Sdk 18.9.0 -> 18.10.0
System.Drawing.Common 10.0.11 -> 10.0.12
System.Security.Cryptography.ProtectedData 10.0.11 -> 10.0.12
Held back:
xunit.v3 stays at 4.0.0. 4.0.1 was published upstream on 2026-09-12
but is not mirrored to the internal feed: an authenticated
`dotnet restore` fails with NU1102 ("Found 30 version(s) ... Nearest
version: 4.0.0"), and the entire 4.0.1 family (.core, .assert,
.common, .extensibility.core, .runner.common, .runner.inproc.console)
is absent.
GitHub.Copilot.SDK stays at 1.0.11. 1.0.13 does resolve from the dev
feed, but the OneBranch feed that #1198 was actually about returns
HTTP 403 for the validating identity, so its availability there is
unproven. This is the exact bump #1198 had to roll back, so it waits
until a restore against that feed can be demonstrated.
The issue's 9-package table is computed against the merge base, not
current main. System.Text.Json and System.Formats.Asn1 already reached
10.0.12 on main via #1211 and #1210, so they are unchanged here.
Validated: full-solution restore against the internal feed (exit 0),
`dotnet build Reactor.slnx --no-restore -c Release` (exit 0, 0 errors),
and `dotnet test tests/Reactor.Tests` (13,996 tests, 0 failed).
Closes #1212
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 9d2eb8aa-59a9-4381-a42d-be6f877130c2
Alexandre Zollinger Chohfi (azchohfi)
added a commit
that referenced
this pull request
Sep 16, 2026
…1216) Applies the bumps from bot/windows-nuget-updates that are provably resolvable from the internal Azure Artifacts feed, and holds back the two that are not. Microsoft.Data.Sqlite 11.0.0-preview.7.26381.103 -> 11.0.0-rc.1.26425.128 Microsoft.Extensions.Logging.Abstractions 10.0.11 -> 10.0.12 Microsoft.NET.Test.Sdk 18.9.0 -> 18.10.0 System.Drawing.Common 10.0.11 -> 10.0.12 System.Security.Cryptography.ProtectedData 10.0.11 -> 10.0.12 Held back: xunit.v3 stays at 4.0.0. 4.0.1 was published upstream on 2026-09-12 but is not mirrored to the internal feed: an authenticated `dotnet restore` fails with NU1102 ("Found 30 version(s) ... Nearest version: 4.0.0"), and the entire 4.0.1 family (.core, .assert, .common, .extensibility.core, .runner.common, .runner.inproc.console) is absent. GitHub.Copilot.SDK stays at 1.0.11. 1.0.13 does resolve from the dev feed, but the OneBranch feed that #1198 was actually about returns HTTP 403 for the validating identity, so its availability there is unproven. This is the exact bump #1198 had to roll back, so it waits until a restore against that feed can be demonstrated. The issue's 9-package table is computed against the merge base, not current main. System.Text.Json and System.Formats.Asn1 already reached 10.0.12 on main via #1211 and #1210, so they are unchanged here. Validated: full-solution restore against the internal feed (exit 0), `dotnet build Reactor.slnx --no-restore -c Release` (exit 0, 0 errors), and `dotnet test tests/Reactor.Tests` (13,996 tests, 0 failed). Closes #1212 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9d2eb8aa-59a9-4381-a42d-be6f877130c2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Reverts the
GitHub.Copilot.SDKversion inDirectory.Packages.propsfrom1.0.13back to1.0.11. One line, nothing else.Why
1.0.13(bumped in #1186) is not published to the internal NuGet feed that the OneBranch CI and release pipelines restore from, so restore fails there.1.0.11is the last version present on that feed.Notes
dotnet restore src/Reactor.Cli/Reactor.Cli.csprojsucceeds on1.0.11.