Allow packages to specify a version range to offer upgrades within

[wtgodbe]

NuGet Product(s) Involved

NuGet.exe, Visual Studio Package Management UI, Visual Studio Package Manager Console

The Elevator Pitch

Today, packages always suggest offering upgrades to the newest version possible. For example, if I depend on Microsoft.Aspnetcore.Components.Webassembly version 6.0.10, Visual Studio's package manager will suggest I upgrade to 7.0.0. However, some packages (e.g. dotnet packages) only contain .dll's for their own TargetFramework, and additionally, a new major version of a package may have API surface area changes that make it incompatible with older major version of a package - therefore the suggested upgrade could break a dev's project. This could also lead them to conclude they should never upgrade, which might make them miss a security update. We should let package authors specify a range of versions within which to offer upgrades, to prevent this from happening and to make sure devs are always being offered the most relevant upgrades for their project.

Additional Context and Details

We've had a lot of requests for this behavior: dotnet/aspnetcore#38336, #5725

Feedback

Please 👍 or 👎 this comment to help us with the direction of this issue & leave as much feedback/questions/concerns as you'd like on this issue itself and we will get back to you shortly.

[MagicAndre1981]

bringing back allowedVersions is already requested years ago and ignored at all.

[nkolev92]

This ask is a duplicate of #6566 and #5725.

The first one tackles the version aspect, the 2nd one talks about the compat aspect.