Migrate to centralized NuGet package management (CPM)#2163
Merged
jeremydmiller merged 1 commit intomainfrom Feb 11, 2026
Merged
Migrate to centralized NuGet package management (CPM)#2163jeremydmiller merged 1 commit intomainfrom
jeremydmiller merged 1 commit intomainfrom
Conversation
Move all package versions into Directory.Packages.props with TFM-conditional groups for Microsoft.Extensions.*, EF Core, Npgsql.EF, and AspNetCore.OpenApi. Normalize version drift across 95 packages, collapse redundant TFM-conditional ItemGroups, fix duplicate entries, and add VersionOverride where projects legitimately need different versions. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Feb 17, 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
1 participant
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
Directory.Packages.propswith centralized version management for all ~95 NuGet packages across 118 project filesVersion=attributes from allPackageReferenceentries in csproj/fsproj files, with versions now governed centrally<PackageVersion>groups for packages that require different versions per target framework (Microsoft.Extensions.*, EF Core, Npgsql.EF, AspNetCore.OpenApi)<ItemGroup>s in Wolverine.csproj, Wolverine.EntityFrameworkCore.csproj, and several test projectsFSharp.CoreandStronglyTypedIdentries in WolverineWebApi.csproj, and a redundant conditional Alba entry in Wolverine.Kafka.Tests.csprojVersionOverridein 3 projects that legitimately need non-central versions (InMemoryMediator, OtelWebApiWolverineMarten, WolverineWebApi)Test plan
dotnet build wolverine.sln --framework net9.0passes with 0 errors🤖 Generated with Claude Code