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
{{ message }}
This repository has been archived by the owner on Feb 23, 2021. It is now read-only.
In absence of a first-class way to "rename" a package on nuget (like NuGet/Home#1590), we should find a way to help users with package renames. It's hard to follow package renames.
Very good idea but not planning to do this in bulk. If we see specific packages where people use the wrong name, we can reconsider this and either create redirect packages for those specific cases, or perhaps do the whole thing.
In absence of a first-class way to "rename" a package on nuget (like NuGet/Home#1590), we should find a way to help users with package renames. It's hard to follow package renames.
Example:
One possible approach: issue an update to an old package that somehow throws a build error that alerts user of the new package name.
Two most recent examples of people confused by our package renames:
dotnet/efcore#5281
dotnet/efcore#5324
The text was updated successfully, but these errors were encountered: