Support pinning with SemVer range

[flcdrg]

I would like to be able to pin a package with a SemVer range.

This would be useful particularly when you want to not upgrade to a newer major version but do upgrade for any new minor versions.

For example if I was using Beyond Compare, but only had a license for v3 then I would not want to take any newer v4.x versions, but if they released a new 3.x then I would want that.

Something like:
choco pin add -n=beyondcompare -version="[3.0,4,0)"

Related

Clickup task.

[ferventcoder]

I've added this - currently pushing this to 1.x.

There is a nice workaround for this now, you could create a package that takes a dependency on BeyondCompare in that range and install it.

[flcdrg]

Yeah, the dependent package would work, except for if you did a choco upgrade all.

[ferventcoder]

It could still work - however the NuGet.Core version we have doesn't really manage this aspect very well.

[ferventcoder]

It would be why it was set up that way for the upgrade all. However I think we could better manage it even in the context of what we have now. Perhaps file an issue?

[ExE-Boss]

I prefer npm’s SemVer range syntax.