`dotnet package update` should respect NuGet version semantics

[Jonany]

Is your feature request related to a problem? Please describe.

dotnet package update in 10.0.100 does not respect NuGet package version semantics such as "*" or "[7.2.0,8.0)". It simply updates everything to the latest version. This limits its usefulness since I then have to manually fix package references and downgrade packages where the version number matters.

Describe the solution you'd like

dotnet package update should respect/follow NuGet version semantics.

Example with ranges:

<PackageReference Include="FluentAssertions" Version="[7.2.0,8.0)" />

If the reference looks like this, the resolved version number should be 7.2.0 (that's the latest for FluentAssertions before 8.0.0) and the version in the PackageReference should not be changed.

Example with "*":

<PackageReference Include="FluentAssertions.Analyzers" Version="*">

If the reference looks like this, the resolved version number should be whatever the latest version that is compatible with the project and package dependencies and the version in the PackageReference should not be changed. At the moment and for this project, it would be 0.34.1.

[dotnet-policy-service]

Thanks for creating this issue! We believe this issue is related to NuGet tooling, which is maintained by the NuGet team. Thus, we closed this one and encourage you to raise this issue in the NuGet repository instead. Don’t forget to check out NuGet’s contributing guide before submitting an issue!

If you believe this issue was closed out of error, please comment to let us know.

Happy Coding!