Repository navigation
Upgrade .NET SDK and dependencies to .NET 11 RC2 - #243
Merged
Merged
Conversation
Align EF tooling and third-party notices with the shipping RC2 versions, and distinguish release metadata from validation builds in the audit skill. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: f6e0d7ca-285b-4ec1-9986-d875c6b3f3e4
There was a problem hiding this comment.
🔵 Needs a closer look
The framework-wide prerelease upgrade passed development validation, but installed win-x64 package startup and trimming remain unverified.
0 open findings
What changed in this PR
Upgrades the repository’s .NET SDK, framework dependencies, tooling, notices, and contributor guidance from .NET 11 RC1 to RC2.
Changes:
- Pins the shipping RC2 SDK and aligned framework packages.
- Updates EF tooling and third-party notices.
- Documents independent release-metadata and WPF package versioning.
| File | Description |
|---|---|
global.json |
Pins .NET 11 RC2. |
Directory.Packages.props |
Aligns framework packages with RC2. |
.config/dotnet-tools.json |
Updates dotnet-ef. |
ThirdPartyNotices.cs |
Synchronizes dependency versions. |
README.md |
Updates source-build requirements. |
.github/copilot-instructions.md |
Updates contributor SDK guidance. |
SKILL.md |
Improves preview-release auditing guidance. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Summary
Update RepoSyncRadar from .NET 11 RC1 to the shipping RC2 SDK and dependencies to pick up runtime and framework reliability fixes while preserving the current application behavior.
11.0.100-rc.2.26504.105; align Microsoft.Extensions, Blazor, EF Core, and dotnet-ef with11.0.0-rc.2.26504.105. Use the independently versioned WPF BlazorWebView package11.0.0-rc.2.26505.5.1.0.21-preview.2, bundled Copilot runtime1.0.97-2, C# 15, Runtime Async, and the existing MTP test configuration unchanged. No application API migration or database schema change was required.Audit evidence and decisions:
26504.105, not the earlier26475.137validation build inbuild-metadata.json. Core packages identify dotnet/dotnet commit820230c386db5b0106c5430b3e5aee92a7826bf5; WPF WebView identifies MAUI commitd32b79928709cf53b671336dabd0caef5a679fc2.Related Issues
N/A - no issue to close.
Scope
Validation
dotnet build RepoSyncRadar.sln -warnaserror -p:RestoreConfigFile=<temporary NuGet.Config>- passed, 0 warnings and 0 errors. The temporary restore configuration was necessary because the existing proxy did not yet contain RC2.dotnet test RepoSyncRadar.sln --no-build --timeout 10m -- --filter-not-trait Category=Manual- passed all 1,505 tests, 0 failures and 0 skipped: App 770, Core 655, Integrations 55, WPF/WebView E2E 25.dotnet ef migrations list --project src\RepoSyncRadar.Core\RepoSyncRadar.Core.csproj --startup-project src\RepoSyncRadar.Core\RepoSyncRadar.Core.csproj --context RadarDbContext --no-build- passed, all five migrations discovered.dotnet ef migrations has-pending-model-changes --project src\RepoSyncRadar.Core\RepoSyncRadar.Core.csproj --startup-project src\RepoSyncRadar.Core\RepoSyncRadar.Core.csproj --context RadarDbContext --no-build- passed, no pending model changes.git diff --check- passed.Restore details: normal
dotnet restore RepoSyncRadar.slnfailed with NU1102 because the configuredazure-defaultproxy lacked RC2 and direct NuGet API connectivity was unavailable. Restore anddotnet tool restorethen succeeded using a temporary source containing 62 exact RC2 packages downloaded from the official NuGet CDN, each SHA-512 checked against its response metadata. Exact-ID package source mapping restricted the fallback; other dependencies used the existing proxy/cache. No user, machine, or repository feed configuration was changed. The temporary feed, packages, configuration, and helper script were removed after validation. A fresh restore in this environment still requires RC2 availability on the approved proxy or the same verified temporary fallback.Risk And Rollback
Release Notes
Release note draft:
Upgrade the build SDK and framework dependencies to .NET 11 RC2, including the matching EF Core tooling and WPF BlazorWebView package. Preserve existing application behavior and synchronize dependency notices and source-build guidance.