koskit
commented
7 months ago @loic-sharma This feature would really help if we could have it. It would match the features on nuget.org
Open Kampfmoehre opened 2 years ago
koskit
commented
7 months ago @loic-sharma This feature would really help if we could have it. It would match the features on nuget.org
Is your feature request related to a problem? Please describe.
We use your cool NuGet server for our internal packages and it is working very nice so far. However we made one of our packages open source and moved it to nuget.org. I would like to add a depcrecatio0n notice to the package in our internal NuGet registry. I looked in the documentation and could not find such a feature for Baget.
Describe the solution you'd like
As far as I can see there seems to be no possibility apart from the official NuGet page to deprecate a package. There is no CLI command for that (analogue to
npm depcrecatefor example), so it seems the functionality must be provided via UI. I know there is no user management or login functionality for BaGet (at least I did not heard of it, correct me if I'm wrong). I guess the most user friendly way to provide a package depcrecation via BaGet would need at least a login, but personally a simple Basic Auth or "enter the API token" Popup would be enough for me.Describe alternatives you've considered
Since there seems to be no way to depcrecate a package via CLI there are not many alternatives to building UI for it. We could open a ticket directly in the dotnet repo to request such a feature, but I think that would take a very long time if it even gets implemented.
Additional context
I know (from the documentation) that I can delete packages but that is not what I want. At least for know, there needs time until all internal projects have adopted the new open source version of the package and for the time given I would like the package to be depcrecated.
Another thing some may want could be an unlist package feature, so it does at least not show up in the search anymore.
For reference: