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
Select a package to deprecate.
Find an alternate package on nuget.org and copy the link.
Paste the link in the Alternate Package box on the deprecation page.
Note the error message.
Expected Behavior
Should be able to add a link to an alternate package
Screenshots
No response
Additional Context and logs
No response
The text was updated successfully, but these errors were encountered:
@sam-wheat
While you can't provide a link in the Alternate Package field, if you enter the Package Id and select a version, it generates a link to that nuget.org package in the Deprecation message.
You can also choose to provide a link in the 'custom message' field, and that should render as a link too.
Package deprecation settings:
Package Details page after deprecating the package:
Sorry about that guys. Not sure why I thought prompt was asking for a link. Changing the prompt to "Alternate Package ID" would make it more clear honestly.
advay26
changed the title
[NuGet.org Bug]: Correct format for alternate package link for a deprecated package
[NuGet.org Bug]: 'Alternate package' field should be clearer that it requires a Package ID
Dec 5, 2024
Impact
It's more difficult to complete my work
Describe the bug
I recently deprecated a package. Tried to add a link to an alternate package and received this message:
Could not find alternate package 'https://www.nuget.org/packages/mypackage'.
Link to alt package was in the format: https://www.nuget.org/packages/mypackage
Repro Steps
Select a package to deprecate.
Find an alternate package on nuget.org and copy the link.
Paste the link in the Alternate Package box on the deprecation page.
Note the error message.
Expected Behavior
Should be able to add a link to an alternate package
Screenshots
No response
Additional Context and logs
No response
The text was updated successfully, but these errors were encountered: