This repository has been archived by the owner. It is now read-only.

Support unpublish workflow for depended on versions #12127

Closed
geek opened this Issue Mar 29, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@geek
Contributor

geek commented Mar 29, 2016

Inspired by @mcollina

This will likely need to be more than a client change, but there are changes we can make to the client to help.

  1. When npm unpublish executes, check the modules that are dependent on the module being unpublished, if any of them are pinned to the specific version being unpublished then proceed to step 2, else, continue with the unpublish procedure as usual
  2. Inform the user that they will break modules with the unpublish command and list out the modules that will break as a result. Prompt the user with a yes/no option to continue. If they type yes, proceed to step 3, otherwise exit
  3. Prompt the user for a reason why they need to unpublish the module version. Email this to support@npmjs.com and inform the user of this action

Ideally, the next step will be for npm support to approve the deletion of the module version and to provide a response to the email. It will be beneficial if the checks in step 1 occur server side, in the registry. But, instead of waiting for that work to be done, there is no reason why we can't perform these checks client side.

@othiym23

This comment has been minimized.

Show comment
Hide comment
@othiym23

othiym23 Apr 8, 2016

Contributor

So, since this went up, npm, Inc. has come up with a policy for handling unpublishes, with an associated discussion thread. I'm closing this feature request in favor of that discussion / policy description, if only because these are all changes happening at the registry level, and not in the CLI. Thanks for your time and the clear policy suggestions, Wyatt!

Contributor

othiym23 commented Apr 8, 2016

So, since this went up, npm, Inc. has come up with a policy for handling unpublishes, with an associated discussion thread. I'm closing this feature request in favor of that discussion / policy description, if only because these are all changes happening at the registry level, and not in the CLI. Thanks for your time and the clear policy suggestions, Wyatt!

@othiym23 othiym23 closed this Apr 8, 2016

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.