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

Conversation

neverett
Copy link
Contributor

In this PR:

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

@neverett neverett requested a review from a team as a code owner August 14, 2018 20:57
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

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.

@neverett
Copy link
Contributor Author

Thanks @ljharb! Updated with your wording.

Copy link
Contributor

@ljharb ljharb left a comment

Choose a reason for hiding this comment

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

Much clearer to me, thanks <3

Copy link
Contributor

@zkat zkat left a comment

Choose a reason for hiding this comment

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

🎉 🐑 🚀 💥

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!

@zkat zkat removed the in-progress label Aug 20, 2018
@zkat zkat changed the base branch from latest to release-next August 20, 2018 22:32
@zkat zkat merged commit 8ed3546 into release-next Aug 20, 2018
@zkat zkat deleted the ne-unpublish branch August 20, 2018 22:33
zkat pushed a commit that referenced this pull request Aug 20, 2018
isaacs added a commit that referenced this pull request Aug 5, 2019
antongolub pushed a commit to antongolub-forks/npm-cli that referenced this pull request May 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants