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.

Sign up for GitHub

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

Jump to bottom

Update republish time and lightly reorganize republish info #48

Merged
merged 3 commits into from
Aug 20, 2018
Merged

Update republish time and lightly reorganize republish info #48

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
28b4da5
update republish time, lightly reorganize info
Aug 14, 2018
4f2bd6f
24 hour republish hold only applies to fully unpublished packages
Aug 17, 2018
8d11df0
Update npm-unpublish.md
zkat Aug 20, 2018
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
11 changes: 5 additions & 6 deletions doc/cli/npm-unpublish.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn’t seem accurate; new versions can be published immediately, altho the old version can never be republished.

Is this a new requirement?

Copy link
Contributor

@iarna iarna Aug 15, 2018 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Entirely unpublished packages have a 24 hour delay before they can be published again. This isn't particularly new, but it's not widely known, thus these docs.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ahhh ok so it’s only if there remains no published versions, then there’s a 24 hour delay?

Maybe the wording here could be like “fully unpublished” or “new versions of packages with every version unpublished”, so it’s clearer?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like that rewording, tbh.

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