Nuget packages are automatically changed to range version with CPM
05:00 08 Jan 2026

I am using central package management CPM in my .net project. I have defined the package like this in the directory.packages.props. But If I update any other nuget package in my solution using nuget package manager. it is also updating the other packages declaration as well, like it has changed to the below format. I am not understanding why is it changing other packages in this format [2.3.0 , ). Is there any benefit of it? Is there a way to tell not do to this conversion?


I am raising this because this can also break the changes, if it consider a higher version than this and if there are some breaking changes with the newer version. It should'nt change it, as I have used the pinned version originally.

Its also causing issue with my dependabot, as dependabot has issues if we give the pacage in the range, it doesnt work as expected. There is also issue reported https://github.com/dependabot/dependabot-core/issues/5204, but that is different story.

c# .net asp.net-core .net-core nuget