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
It seems there is a typo in the version 2.71828—it should be 2.7.1828, not 2.71828. This mistake causes confusion since 2.71828 appears greater than 2.8 when compared numerically. This can easily mislead developers into updating to the wrong version. Also, the new developers always install it by mistake and encounter many legacy issues, killing time to find out.
Resolution:
Please unlist 2.71828 manually from the NuGet server to prevent further confusion.
Steps to Reproduce
Did you find any workaround?
Please unlist 2.71828 from the NuGet server to prevent further confusion.
Relevant log output
The text was updated successfully, but these errors were encountered:
While we wish this was indeed a mistake on our part, it is not. It is how Square did their Java library versioning and it messes up Java/Maven as well:
Can we unlist it from the nuget server? So it will be available for older versions and anyone who needs it, but it also won't appear on the search and upgrades.
Android framework version
net9.0-android
Affected platform version
All Version
Description
There is an incorrect version number for Square.Picasso on the public NuGet server: 2.71828.
Recent version: 2.8.0.16
Problematic version: 2.71828
It seems there is a typo in the version 2.71828—it should be 2.7.1828, not 2.71828. This mistake causes confusion since 2.71828 appears greater than 2.8 when compared numerically. This can easily mislead developers into updating to the wrong version. Also, the new developers always install it by mistake and encounter many legacy issues, killing time to find out.
Resolution:
Please unlist 2.71828 manually from the NuGet server to prevent further confusion.
Steps to Reproduce
Did you find any workaround?
Please unlist 2.71828 from the NuGet server to prevent further confusion.
Relevant log output
The text was updated successfully, but these errors were encountered: