Install-Package should filter unlisted packages when no version is given

[skofman1]

@jsakamoto commented on Wed Apr 19 2017

What you were trying to do.

Update the NuGet package "Selenium.WebDriver.MicrosoftWebDriver" from version v.10.0.14393.1 to latest version.

What you expected to happen.

The version of the NuGet package "Selenium.WebDriver.MicrosoftWebDriver" update to v.10.0.15063.0.

What actually happened.

The version of the NuGet package "Selenium.WebDriver.MicrosoftWebDriver" updated to v.10.1.14393.0.

That version is unlisted package version.
See also: https://www.nuget.org/packages/Selenium.WebDriver.MicrosoftWebDriver/10.1.14393

Steps to reproduce the problem.

1. Create or open any .NET project with Visual Studio 2017.
2. Execute "Install-Package Selenium.WebDriver.MicrosoftWebDriver" command at Package Manager Console.
3. After it, the correct latest version "10.0.15063" was installed. (This is correct behavior)
4. Next step, execute "Update-Package Selenium.WebDriver.MicrosoftWebDriver" command.
5. Then, the command update the package to UNLISTED version "10.1.14393" !

Appendix Information

I guess, this problem happens due to the JSON response from api.nuget.org.

The JSON reponse contains "upper" proprty, but it looks like include unlisted package versions.

Is it by design and it should not change? or should fix it?

---

@skofman1 commented on Wed Apr 19 2017

@joelverhagen , @emgarten , is this a client or server issue?

---

@emgarten commented on Wed Apr 19 2017

Looks like a client issue if the unlisted package is being installed. The upper and lower bounds are correct.

---

@joelverhagen commented on Wed Apr 19 2017

I confirmed this behavior in NuGet 4.2.0.2451 with a packages.config project. A PackageReference project does not reproduce the problem. The issue occurs for both V2 and V3 NuGet.org source URL.

As @emgarten, this seems to be a client issue.

[wli3]

Hi,
dotnet CLI got an opposite issue

https://github.com/dotnet/cli/issues/7492

Which should be the designed behavior? Latest unlisted of listed?

[richardszalay]

FYI, the CLI issue is the same issue. Perhaps you meant "equivalent", instead of "opposite"?

[richardszalay]

I'd say this is definitely a bug, and not designed behavior. The documentation for unlisting a package even says:

Unlisting a version can help you prevent new usage of it without breaking dependent projects and builds

And having it install by default does quite the opposite of preventing new usage.

[tokyo0709]

Experiencing the same issue, https://stackoverflow.com/questions/46977808/updating-nuget-package-yields-unlisted-version

[karann-msft]

cc: @anangaur

[jainaashish]

dupe of #4553

[matkoch]

5.3.0 is still downloading unlisted versions?

@jainaashish please reopen

[matkoch]

@emgarten ^^^^

[nkolev92]

@matkoch If you think there's a regression please open a new issue since this is not actively monitored.

[matkoch]

@nkolev92 there already is another one at #7466

I just can't understand how this is not addressed for such a long time? Sorry, but I'm really disappointed.

[mwwhited]

5 years later and this is still and issue. I should really sell my MS stock.

[nkolev92]

@mwwhited
This issue is closed. The linked issue for PMC, #4553, was fixed in 2018 NuGet/NuGet.Client#2270.