Update range dependencies

[bkohler_1524]

We are looking to use ranges as dependencies. If when we upload we select a range of 1.0.1 or newer how can we update it if the end range now has a cap.

For example, product A version 1.0.0 works with all versions of product B after 1.1.0. We then release product A version 2.0.0 and it works with all version of product B after 2.0.0, but Product A does not work with product B 1.1.0. We now need to add an end range on the dependency of product B to be 1.1.0 thru 1.9.0.

I did see a previous discussion, but I don't think our use case was addressed Update Dependencies for older version of NuGet package in ProGet

[atripp]

Hello @bkohler_1524,

Because packages are immutable, you need to decide the future-compatibility at the time you create the package. This is where Semantic Versioning dependencies can really help.

Following the rules of SemVer, you can say that "ProductA 1.0.0 has a dependency on ProductB (1.1.0-2.0.0]", what that means is that you can use every version of ProductB from 1.1.10 up to (but not including) 2.0.0.

This allows you to make as many minor versions of ProductB (such as 1.200.0) before "breaking" compatibility.

If these version numbers are business/marketing-driven, and it's impossible to change their mind on versioning, you can always maintain an internal version number - this is what many products (such as Microsoft) does.