Migrate to Centralized NuGet Package Management (CPM)

[Copilot]

• Create Directory.Packages.props at repo root with all 22 unique packages sorted alphabetically
• Update all 7 .csproj files – remove Version from all <PackageReference> elements
• Add Directory.Packages.props to the Misc solution folder in CliFx.sln
• Verify build succeeds

Original prompt

Migrate to Centralized NuGet Package Management (CPM)

Migrate the repository from per-project Version attributes on <PackageReference> to NuGet's Centralized Package Management (CPM).

What to do

1. Create a Directory.Packages.props file at the root of the repository with <ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally> and a <PackageVersion> entry for every unique package used across all .csproj files. Use the version already present in the .csproj files.

2. Update all .csproj files to remove the Version="..." attribute from every <PackageReference> element (CPM now manages the version centrally). Keep all other attributes (e.g. PrivateAssets, Condition, ExcludeAssets, etc.) intact.

3. Do not change any TargetFramework(s), project structure, or anything unrelated to package versioning.

Reference

See how it was done in the sibling repo Tyrrrz/YoutubeExplode PR #940: Tyrrrz/YoutubeExplode#940

Notes

• If a package appears with different versions in different projects, use the highest version and make a note in the PR description.
• <PackageVersion> entries in Directory.Packages.props should be sorted alphabetically.
• Make sure the file includes a valid MSBuild props file <Project> root element.
• Preserve all Condition attributes on <PackageReference> elements.
• Use VersionOverride for any Roslyn analyzer packages that need a specific version per-project.

This pull request was created from Copilot chat.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[Tyrrrz]

@copilot add the created Directory.Packages.props file to the sln file

[Copilot]

Pull request overview

This PR migrates the solution to NuGet Central Package Management (CPM) by centralizing all package versions into a root Directory.Packages.props, removing per-project Version="..." attributes while preserving existing reference metadata (e.g., PrivateAssets, Condition).

Changes:

• Added Directory.Packages.props with ManagePackageVersionsCentrally enabled and centralized <PackageVersion> entries.
• Updated all .csproj files to remove per-PackageReference Version attributes in favor of CPM.
• Preserved the Roslyn analyzer lower-version constraint via VersionOverride in CliFx.Analyzers.csproj.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
Directory.Packages.props	Introduces CPM and centralizes all NuGet package versions.
CliFx/CliFx.csproj	Removes per-reference versions; keeps conditional reference attributes intact.
CliFx.Tests/CliFx.Tests.csproj	Removes per-reference versions for test dependencies.
CliFx.Tests.Dummy/CliFx.Tests.Dummy.csproj	Removes per-reference version for build-time tooling dependency.
CliFx.Demo/CliFx.Demo.csproj	Removes per-reference versions for demo dependencies.
CliFx.Benchmarks/CliFx.Benchmarks.csproj	Removes per-reference versions for benchmark dependencies.
CliFx.Analyzers/CliFx.Analyzers.csproj	Uses VersionOverride for Roslyn packages to preserve lowest-compiler targeting.
CliFx.Analyzers.Tests/CliFx.Analyzers.Tests.csproj	Removes per-reference versions for analyzer test dependencies.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

@copilot add the created Directory.Packages.props file to the sln file

Done in 7d9d8d8 — Directory.Packages.props is now listed under the Misc solution folder alongside Directory.Build.props.