diff options
author | Nikki Everett <neverett@users.noreply.github.com> | 2018-08-21 01:33:21 +0300 |
---|---|---|
committer | Kat Marchán <kzm@zkat.tech> | 2018-08-21 02:17:49 +0300 |
commit | 95031b90ce0b0c4dcd5e4eafc86e3e5bfd59fb3e (patch) | |
tree | 4bfb0c0124b1e81d29348f44777ff3b85124885e | |
parent | 0e576f0aa6ea02653d948c10f29102a2d4a31944 (diff) |
docs: Update republish time and lightly reorganize republish info (#48)
PR-URL: https://github.com/npm/cli/pull/48
Credit: @neverett
Reviewed-By: @zkat
-rw-r--r-- | doc/cli/npm-unpublish.md | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/doc/cli/npm-unpublish.md b/doc/cli/npm-unpublish.md index 57df24d1a..b5b02154e 100644 --- a/doc/cli/npm-unpublish.md +++ b/doc/cli/npm-unpublish.md @@ -24,14 +24,15 @@ If no version is specified, or if all versions are removed then the root package entry is removed from the registry entirely. Even if a package version is unpublished, that specific name and -version combination can never be reused. In order to publish the -package again, a new version number must be used. +version combination can never be reused. In order to publish the +package again, a new version number must be used. Additionally, +new versions of packages with every version unpublished may not +be republished until 24 hours have passed. With the default registry (`registry.npmjs.org`), unpublish is -only allowed with versions published in the last 72 hours. Similarly, -new versions of unpublished packages may not be republished until 72 hours -have passed. If you are trying to unpublish a version published longer -ago than that, contact support@npmjs.com. +only allowed with versions published in the last 72 hours. If you +are trying to unpublish a version published longer ago than that, +contact support@npmjs.com. The scope is optional and follows the usual rules for `npm-scope(7)`. |