Update republish time and lightly reorganize republish info by neverett · Pull Request #48 · npm/cli

neverett · 2018-08-14T20:57:52Z

In this PR:

Update to correct package republish time (24 hours)
Light reorganization of republish info for clarity

ljharb · 2018-08-15T01:18:43Z

-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


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

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.

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?

I like that rewording, tbh.

neverett · 2018-08-17T16:57:47Z

Thanks @ljharb! Updated with your wording.

ljharb

Much clearer to me, thanks <3

zkat

🎉 🐑 🚀 💥

The only thing that'd be nice is if you wrapped the modified lines to the same length as their surrounding lines, but that's not a big deal if you don't get around to it.

Thank you!

@neverett

PR-URL: #48 Credit: @neverett Reviewed-By: @zkat

@mterrel

…npm#48) * fix(auth): support --help / -h flag on auth subcommand (fixesnpm#26) * add changeset

neverett · 2018-08-14T20:57:52Z

In this PR:

Update to correct package republish time (24 hours)
Light reorganization of republish info for clarity

ljharb · 2018-08-15T01:18:43Z

-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


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

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.

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?

I like that rewording, tbh.

neverett · 2018-08-17T16:57:47Z

Thanks @ljharb! Updated with your wording.

ljharb

Much clearer to me, thanks <3

zkat

🎉 🐑 🚀 💥

The only thing that'd be nice is if you wrapped the modified lines to the same length as their surrounding lines, but that's not a big deal if you don't get around to it.

Thank you!

@neverett

PR-URL: #48 Credit: @neverett Reviewed-By: @zkat

@mterrel

…npm#48) * fix(auth): support --help / -h flag on auth subcommand (fixesnpm#26) * add changeset

neverett · 2018-08-14T20:57:52Z

In this PR:

Update to correct package republish time (24 hours)
Light reorganization of republish info for clarity

ljharb · 2018-08-15T01:18:43Z

-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


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

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.

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?

I like that rewording, tbh.

neverett · 2018-08-17T16:57:47Z

Thanks @ljharb! Updated with your wording.

ljharb

Much clearer to me, thanks <3

zkat

🎉 🐑 🚀 💥

The only thing that'd be nice is if you wrapped the modified lines to the same length as their surrounding lines, but that's not a big deal if you don't get around to it.

Thank you!

@neverett

PR-URL: #48 Credit: @neverett Reviewed-By: @zkat

@mterrel

…npm#48) * fix(auth): support --help / -h flag on auth subcommand (fixesnpm#26) * add changeset

neverett · 2018-08-14T20:57:52Z

In this PR:

Update to correct package republish time (24 hours)
Light reorganization of republish info for clarity

ljharb · 2018-08-15T01:18:43Z

-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


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

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.

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?

I like that rewording, tbh.

neverett · 2018-08-17T16:57:47Z

Thanks @ljharb! Updated with your wording.

ljharb

Much clearer to me, thanks <3

zkat

🎉 🐑 🚀 💥

The only thing that'd be nice is if you wrapped the modified lines to the same length as their surrounding lines, but that's not a big deal if you don't get around to it.

Thank you!

@neverett

PR-URL: #48 Credit: @neverett Reviewed-By: @zkat

@mterrel

…npm#48) * fix(auth): support --help / -h flag on auth subcommand (fixesnpm#26) * add changeset

neverett · 2018-08-14T20:57:52Z

In this PR:

Update to correct package republish time (24 hours)
Light reorganization of republish info for clarity

ljharb · 2018-08-15T01:18:43Z

-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


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

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.

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?

I like that rewording, tbh.

neverett · 2018-08-17T16:57:47Z

Thanks @ljharb! Updated with your wording.

ljharb

Much clearer to me, thanks <3

zkat

🎉 🐑 🚀 💥

The only thing that'd be nice is if you wrapped the modified lines to the same length as their surrounding lines, but that's not a big deal if you don't get around to it.

Thank you!

@neverett

PR-URL: #48 Credit: @neverett Reviewed-By: @zkat

@mterrel

…npm#48) * fix(auth): support --help / -h flag on auth subcommand (fixesnpm#26) * add changeset

neverett · 2018-08-14T20:57:52Z

In this PR:

Update to correct package republish time (24 hours)
Light reorganization of republish info for clarity

ljharb · 2018-08-15T01:18:43Z

-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


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

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.

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?

I like that rewording, tbh.

neverett · 2018-08-17T16:57:47Z

Thanks @ljharb! Updated with your wording.

ljharb

Much clearer to me, thanks <3

zkat

🎉 🐑 🚀 💥

The only thing that'd be nice is if you wrapped the modified lines to the same length as their surrounding lines, but that's not a big deal if you don't get around to it.

Thank you!

@neverett

PR-URL: #48 Credit: @neverett Reviewed-By: @zkat

@mterrel

…npm#48) * fix(auth): support --help / -h flag on auth subcommand (fixesnpm#26) * add changeset

neverett · 2018-08-14T20:57:52Z

In this PR:

Update to correct package republish time (24 hours)
Light reorganization of republish info for clarity

ljharb · 2018-08-15T01:18:43Z

-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


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

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.

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?

I like that rewording, tbh.

neverett · 2018-08-17T16:57:47Z

Thanks @ljharb! Updated with your wording.

ljharb

Much clearer to me, thanks <3

zkat

🎉 🐑 🚀 💥

The only thing that'd be nice is if you wrapped the modified lines to the same length as their surrounding lines, but that's not a big deal if you don't get around to it.

Thank you!

@neverett

PR-URL: #48 Credit: @neverett Reviewed-By: @zkat

@mterrel

…npm#48) * fix(auth): support --help / -h flag on auth subcommand (fixesnpm#26) * add changeset

neverett · 2018-08-14T20:57:52Z

In this PR:

Update to correct package republish time (24 hours)
Light reorganization of republish info for clarity

ljharb · 2018-08-15T01:18:43Z

-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


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

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.

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?

I like that rewording, tbh.

neverett · 2018-08-17T16:57:47Z

Thanks @ljharb! Updated with your wording.

ljharb

Much clearer to me, thanks <3

zkat

🎉 🐑 🚀 💥

The only thing that'd be nice is if you wrapped the modified lines to the same length as their surrounding lines, but that's not a big deal if you don't get around to it.

Thank you!

@neverett

PR-URL: #48 Credit: @neverett Reviewed-By: @zkat

@mterrel

…npm#48) * fix(auth): support --help / -h flag on auth subcommand (fixesnpm#26) * add changeset

update republish time, lightly reorganize info
28b4da5

neverett requested a review from a team as a code owner August 14, 2018 20:57

ljharb reviewed Aug 15, 2018
View reviewed changes

zkat added in-progress labels Aug 15, 2018

24 hour republish hold only applies to fully unpublished packages
4f2bd6f

ljharb approved these changes Aug 17, 2018
View reviewed changes

zkat approved these changes Aug 20, 2018
View reviewed changes

zkat removed the in-progress label Aug 20, 2018

Update npm-unpublish.md
8d11df0

zkat changed the base branch from latest to release-nextAugust 20, 2018 22:32

zkat merged commit 8ed3546 into release-nextAug 20, 2018

zkat deleted the ne-unpublish branch August 20, 2018 22:33

zkat pushed a commit that referenced this pull request Aug 20, 2018
docs: Update republish time and lightly reorganize republish info (#48)
95031b9
PR-URL: #48 Credit: @neverett Reviewed-By: @zkat

kevinjm39 mentioned this pull request May 1, 2022
[Snyk] Upgrade @npmcli/config from 4.0.0 to 4.0.2 kevinjm39/cli#4
Open

snyk-bot mentioned this pull request Jul 8, 2022
[Snyk] Upgrade npm-profile from 6.0.3 to 6.1.0 LadyK-21/cli#10
Open

hojatA1 mentioned this pull request Jun 23, 2023
[Snyk] Fix for 1 vulnerabilities hojatA1/npm.cli#26
Open

EMWickd mentioned this pull request Jun 24, 2023
[Snyk] Fix for 1 vulnerabilities EMWickd/cli#30
Open

gutwrinch mentioned this pull request Oct 20, 2023
[Snyk] Upgrade @npmcli/package-json from 3.1.1 to 5.0.0 gutwrinch/cli-1#8
Open

CALISOULB mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities CALISOULB/cli#19
Open

This was referenced Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities varmakarthik12/cli#30
Closed
[Snyk] Fix for 1 vulnerabilities varmakarthik12/cli#38
Closed

MrBrain295 mentioned this pull request Dec 19, 2023
[Snyk] Fix for 3 vulnerabilities MrBrain295/cli#12
Open

CALISOULB mentioned this pull request Dec 20, 2023
[Snyk] Fix for 1 vulnerabilities CALISOULB/cli#21
Open

gutwrinch mentioned this pull request Jan 6, 2024
[Snyk] Upgrade p-map from 4.0.0 to 7.0.0 gutwrinch/cli-1#20
Open

Kingcrypto38 mentioned this pull request Jan 11, 2024
[Snyk] Upgrade p-map from 4.0.0 to 7.0.0 Kingcrypto38/cli#1
Open

antongolub pushed a commit to antongolub-forks/npm-cli that referenced this pull request May 18, 2024
fix: linting (npm#48)
163f021

seanmozeik mentioned this pull request Dec 25, 2025
Expo Run fails ecrindigital/facetpack#3
Closed

Jah-yee pushed a commit to Jah-yee/cli that referenced this pull request Apr 16, 2026
fix(auth): support --help / -h flag on auth subcommand (fixesnpm#26) (…
666f9a8
…npm#48) * fix(auth): support --help / -h flag on auth subcommand (fixesnpm#26) * add changeset

github-actionsBot referenced this pull request in Kevinlee7250/cli Jun 12, 2026
📊 대시보드 데이터 업데이트 (#48)
b0c4d54

github-actionsBot referenced this pull request in Kevinlee7250/cli Jul 1, 2026
🤖 봇 응답 (#48)
f59d873

github-actionsBot referenced this pull request in Kevinlee7250/cli Jul 8, 2026
🔧 자동 수리 완료 (#48)
0b89673

github-actionsBot referenced this pull request in Kevinlee7250/cli Jul 29, 2026
🔥 트렌드 선점 후보 갱신 (#48)
1f93f2a

github-actionsBot referenced this pull request in Kevinlee7250/cli Aug 26, 2026
🔍 구글 색인 상태 리포트 (#48)
8f59c54