search

denoland / website_feedback

For reporting issues & suggestions for deno.com and deno.land
9 stars 1 forks source link

deprecating modules on https://deno.land/x #7

Open panva opened 1 year ago

panva commented 1 year ago

Background: I've renamed a module of mine and successfully registered a second webhook for the new module name. doauth is the old, oauth4webapi is the new. See https://deno.land/x?query=openid+connect

What is the correct procedure to deprecate modules on deno.land/x? Can a module be hidden from search results? Should I remove the webhook for the old name?

kitsonk commented 1 year ago

The registry is intended to be immutable. The best way to deprecate a module is to update the README and push a tag indicating that the module is deprecated. For example: https://deno.land/x/media_types@v2.13.0.

panva commented 1 year ago

The registry and its frontend are two entirely separate entities.

I'm 100% expecting the code to remain in the registry.

At the same time I am expecting the frontend to have moderation capabilities which could support a simple act of hiding a package from api search results and robot queries.