You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a bug in the latest version of NuGet (that shipped with .NET Core 2) that causes the "unlisted" property to be ignored on the highest version of a package when no version is specified. This is causing mockhttp 3.0 (published in error of version 1.3) to be installed at an increasingly large scale.
The NuGet bug has been marked with Priority:1, but I don't think mockhttp should wait for it to be fixed. Instead, version 1.5.1 will be released as 3.1 with this issue being the only resolved change.
The text was updated successfully, but these errors were encountered:
There is a bug in the latest version of NuGet (that shipped with .NET Core 2) that causes the "unlisted" property to be ignored on the highest version of a package when no version is specified. This is causing mockhttp 3.0 (published in error of version 1.3) to be installed at an increasingly large scale.
The NuGet bug has been marked with Priority:1, but I don't think mockhttp should wait for it to be fixed. Instead, version 1.5.1 will be released as 3.1 with this issue being the only resolved change.
The text was updated successfully, but these errors were encountered: