summaryrefslogtreecommitdiff
path: root/deps/npm/man/man1/npm-unpublish.1
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/man/man1/npm-unpublish.1')
-rw-r--r--deps/npm/man/man1/npm-unpublish.115
1 files changed, 8 insertions, 7 deletions
diff --git a/deps/npm/man/man1/npm-unpublish.1 b/deps/npm/man/man1/npm-unpublish.1
index 19654ab7a3..0a7c8f28a1 100644
--- a/deps/npm/man/man1/npm-unpublish.1
+++ b/deps/npm/man/man1/npm-unpublish.1
@@ -1,4 +1,4 @@
-.TH "NPM\-UNPUBLISH" "1" "July 2018" "" ""
+.TH "NPM\-UNPUBLISH" "1" "August 2018" "" ""
.SH "NAME"
\fBnpm-unpublish\fR \- Remove a package from the registry
.SH SYNOPSIS
@@ -26,14 +26,15 @@ If no version is specified, or if all versions are removed then
the root package entry is removed from the registry entirely\.
.P
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\.
.P
With the default registry (\fBregistry\.npmjs\.org\fP), 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 \|\.
+only allowed with versions published in the last 72 hours\. If you
+are trying to unpublish a version published longer ago than that,
+contact \|\.
.P
The scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fP\|\.
.SH SEE ALSO