Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update republish time and lightly reorganize republish info #48

Merged
merged 3 commits into from
Aug 20, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions doc/cli/npm-unpublish.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 [email protected].
only allowed with versions published in the last 72 hours. If you
are trying to unpublish a version published longer ago than that,
contact [email protected].

The scope is optional and follows the usual rules for `npm-scope(7)`.

Expand Down