Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/IdentityProvider/IdentityProvider.csproj
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@

<ItemGroup>
<PackageReference Include="Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore" Version="9.0.4" />
<PackageReference Include="Microsoft.AspNetCore.Identity.EntityFrameworkCore" Version="9.0.3" />
<PackageReference Include="Microsoft.AspNetCore.Identity.EntityFrameworkCore" Version="9.0.13" />
Copy link

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

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

This bumps Microsoft.AspNetCore.Identity.EntityFrameworkCore to 9.0.13, but the project still pins related ASP.NET Core/EF Core packages to 9.0.3/9.0.4 (e.g., Microsoft.EntityFrameworkCore, *.Design, *.Tools, *.Sqlite, Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore). Mixing patch versions in this tightly-coupled stack can trigger NuGet downgrade/restore issues and makes runtime assembly resolution harder to reason about. Consider aligning all Microsoft.AspNetCore.*EntityFrameworkCore and Microsoft.EntityFrameworkCore.* references in this project to the same patch version (ideally 9.0.13).

Copilot uses AI. Check for mistakes.
<PackageReference Include="Microsoft.EntityFrameworkCore" Version="9.0.4" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Design" Version="9.0.3">
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
Expand Down