NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet
NuGet, #1978 most downloaded on NuGet
Provides the ability to centrally manage your NuGet package versions when using PackageReference.
Latest stable
2.1.3
Last release 5 years ago
no release in 18 months
Release timing varies
gaps range from 2 weeks to 1.5 years
Nearly every release is documented
notes for 14 of 15 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
15 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
Revert "Fix issue with CentralPackageVersions logging error when using a custom import pattern" by @jeffkl in https://github.com/microsoft/MSBuildSdks
Full Changelog: https://github.com/microsoft/MSBuildSdks/compare/Microsoft.Build.CentralPackageVersions.2.1.2...Microsoft.Build.CentralPackageVersions.2.1.3
Fix issue with CentralPackageVersions logging error when using a custom import pattern. by @jeffkl in https://github.com/microsoft/MSBuildSdks/pull/32
Full Changelog: https://github.com/microsoft/MSBuildSdks/compare/Microsoft.Build.CentralPackageVersions.2.1.1...Microsoft.Build.CentralPackageVersions.2.1.2
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Fix restore in Traversal when TargetFrameworks property is set
Full Changelog: https://github.com/microsoft/MSBuildSdks/compare/Microsoft.Build.CentralPackageVersions.2.0.147...Microsoft.Build.CentralPackageVersions.2.1.1
Use license expression instead of embedding license in packages by @jeffkl in https://github.com/microsoft/MSBuildSdks/pull/315
Full Changelog: https://github.com/microsoft/MSBuildSdks/compare/Microsoft.Build.CentralPackageVersions.2.0.79...Microsoft.Build.CentralPackageVersions.2.0.147
Disallow orphaned VersionOverrides (opt-in) (#180) Thanks @erikness!
Add BuildMultitargeting and BuildTransitive to IncludeAssets for GlobalPackageReference
Mark Microsoft.AspNetCore.App and Microsoft.AspNetCore.All as implicitly defined
Nothing published for this version
Allow CentralPackageVersions to be explicitly enabled
Add workaround for FSharp SDK not marking implicit packages as IsImplicitlyDefined
Disable CentralPackageVersions for .nuproj projects
Disable CentralPackageVersions for projects that use packages.config or do not support PackageReference
Use item Artifact intead of Artifacts
The <Artifacts /> item has been renamed to <Artifact />.
In version 2.0 of the package, we have deprecated the PackageVersion item and instead are using <PackageReference Update="Package" />. To migrate an existing code base to use the newer version, please do the following:
PackageVersion Include with PackageReference Update in your Packages.props<br/>
v1.0:<ItemGroup>
<PackageVersion Include="PackageA" Version="1.0.0" />
</ItemGroup>
v2.0:<ItemGroup>
<PackageReference Update="PackageA" Version="1.0.0" />
</ItemGroup>
PackageVersion items in Packages.props for global package references and instead specify the version on the <GlobalPackageReference /> item<br/>
v1.0:<ItemGroup>
<PackageVersion Include="PackageA" Version="1.0.0" />
<GlobalPackageReference Include="PackageA" />
</ItemGroup>
v2.0:<ItemGroup>
<GlobalPackageReference Include="PackageA" Version="1.0.0" />
</ItemGroup>
PackageVersion items in individual projects, set VersionOverride to override a version, and move metadata to the corresponding <PackageReference/> item in the project file.<br/>
v1.0:<ItemGroup>
<PackageVersion Include="PackageA" Version="1.0.0" ExcludeAssets="Build" />
<PackageReference Include="PackageA" />
</ItemGroup>
v2.0:<ItemGroup>
<PackageReference Include="PackageA" VersionOverride="1.0.0" ExcludeAssets="Build" />
</ItemGroup>
Fixes issues related to SDK-style projects and non-existent targets
https://www.nuget.org/packages/Microsoft.Build.Traversal/1.0.34
# What's New * Initial release
One column per quarter.