From 28b4da5fb76b52fb87ebfdac6edd3e4ef4710c51 Mon Sep 17 00:00:00 2001 From: Nikki Everett Date: Tue, 14 Aug 2018 13:56:02 -0700 Subject: [PATCH 1/3] update republish time, lightly reorganize info --- doc/cli/npm-unpublish.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/cli/npm-unpublish.md b/doc/cli/npm-unpublish.md index 57df24d1a0c37..40096f49864d5 100644 --- a/doc/cli/npm-unpublish.md +++ b/doc/cli/npm-unpublish.md @@ -24,14 +24,13 @@ 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 unpublished packages 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)`. From 4f2bd6f9a10d128ecd439234035c33a5665ebd4f Mon Sep 17 00:00:00 2001 From: Nikki Everett Date: Fri, 17 Aug 2018 09:55:48 -0700 Subject: [PATCH 2/3] 24 hour republish hold only applies to fully unpublished packages --- doc/cli/npm-unpublish.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/cli/npm-unpublish.md b/doc/cli/npm-unpublish.md index 40096f49864d5..5b47a320e1965 100644 --- a/doc/cli/npm-unpublish.md +++ b/doc/cli/npm-unpublish.md @@ -26,8 +26,7 @@ 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. Additionally, -new versions of unpublished packages may not be republished until 24 hours -have passed. +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. If you are trying to unpublish a version published longer ago than that, contact support@npmjs.com. From 8d11df0909f92796063e85dabde476fcd62c83a0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kat=20March=C3=A1n?= Date: Mon, 20 Aug 2018 15:32:36 -0700 Subject: [PATCH 3/3] Update npm-unpublish.md --- doc/cli/npm-unpublish.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/doc/cli/npm-unpublish.md b/doc/cli/npm-unpublish.md index 5b47a320e1965..b5b02154e9309 100644 --- a/doc/cli/npm-unpublish.md +++ b/doc/cli/npm-unpublish.md @@ -26,10 +26,13 @@ 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. Additionally, -new versions of packages with every version unpublished may not be republished until 24 hours have passed. +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. 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)`.