Repository navigation
Bring the .NET 10 package family to 10.0.14 (supersedes #52 and #48) - #57
Merged
Merged
Conversation
Dependabot opened #52 and #48 to move Microsoft.EntityFrameworkCore, Microsoft.Extensions.DependencyInjection and Microsoft.Extensions.Logging to 10.0.14, each touching only the Infrastructure project and leaving the rest of the framework on 10.0.13. A release should not ship two servicing levels of one framework side by side (see 43c84ae, which did the same alignment for 10.0.13), and mixing EntityFrameworkCore 10.0.14 with EntityFrameworkCore.Design/Sqlite 10.0.13 would trip NU1605 once rebased on main. This moves every 10.0.13 reference across all five projects to 10.0.14 in one go: EF Core (runtime, Design, Sqlite), the Microsoft.Extensions.* packages (Configuration, DependencyInjection, Logging, Options.ConfigurationExtensions, Caching.Memory, Hosting.Systemd, Hosting.WindowsServices) and System.DirectoryServices(.AccountManagement). Third-party and separately versioned packages (Npgsql 10.0.3, FluentValidation 12.2.0, MediatR 12.5.0, Novell LDAP, the test tooling) are left as they are. restore and build -warnaserror are clean; dotnet test passes 945, 0 failed, 14 skipped (Postgres/Samba, which need live servers). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Nov 6, 2026
Nelsar
approved these changes
Nov 6, 2026
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.
Replaces the partial Dependabot bumps #52 and #48, which each touched only the Infrastructure project and left the rest of the .NET 10 framework on 10.0.13.
Why not merge #52 / #48 as-is
Microsoft.EntityFrameworkCore+ twoMicrosoft.Extensions.*packages to 10.0.14 while leavingEntityFrameworkCore.Design,EntityFrameworkCore.Sqlite,Microsoft.Extensions.Configuration/Options.ConfigurationExtensions/Caching.Memory/Hosting.*andSystem.DirectoryServices*on 10.0.13. A release should not ship two servicing levels of one framework side by side — the same reasoning as43c84ae, which aligned everything to 10.0.13 for 0.3.0.Microsoft.Extensions.* >= 10.0.14pulling against direct 10.0.13 pins, would tripNU1605(build treats it as error) once rebased on current main — the same failure class that blocked Bump Microsoft.AspNetCore.Mvc.Testing from 10.0.13 to 10.0.14 #47.mainafter the test-stack and MediatR merges.What this does
Moves every 10.0.13 reference across all five projects to 10.0.14 in one consistent step:
Microsoft.EntityFrameworkCore,.Design,.SqliteMicrosoft.Extensions.*: Configuration, DependencyInjection, Logging, Options.ConfigurationExtensions, Caching.Memory, Hosting.Systemd, Hosting.WindowsServicesSystem.DirectoryServices,System.DirectoryServices.AccountManagementLeft untouched (separate version trains / third-party):
Npgsql.EntityFrameworkCore.PostgreSQL10.0.3,System.IdentityModel.Tokens.Jwt8.21.0,Novell.Directory.Ldap.NETStandard3.6.0, FluentValidation 12.2.0, MediatR 12.5.0, and the test tooling.Microsoft.AspNetCore.Authentication.JwtBearerand the test stack were already at 10.0.14.Verified locally
dotnet restore+dotnet build -warnaserrorclean (0 warnings, 0 errors);dotnet test→ 945 passed, 0 failed, 14 skipped (Postgres/Samba need live servers).