Repository navigation
Wait for npm to serve a new version before tagging - #2
Merged
Merged
Conversation
npm now processes a published version for a few minutes before the registry serves it, so the tag job polls for the gitHead for up to 15 minutes instead of failing immediately.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
npm processes a newly published version for a few minutes before the registry serves it. The 0.2.0 tag job ran seconds after publishing, found no gitHead and failed; a rerun a few minutes later succeeded. The tag job now polls the registry for up to 15 minutes (job timeout raised to 20).
Release
Verification