[CI] Publish to release channels sequentially#20827
Merged
acdlite merged 1 commit intofacebook:masterfrom Feb 16, 2021
Merged
Conversation
npm will sometimes fail if you try to concurrently publish two different versions of the same package, even if they use different dist tags. So instead of publishing to the Next and Experimental channels simultaneously, we'll do them one after the other. If we did want to speed up these publish workflows, we could paralellize by package instead of by release channel.
facebook-github-bot
added
CLA Signed
React Core Team
|
Comparing: 1a74726...2429f74 Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: (No significant changes) |
koto
pushed a commit
to koto/react
that referenced
this pull request
Jun 15, 2021
npm will sometimes fail if you try to concurrently publish two different versions of the same package, even if they use different dist tags. So instead of publishing to the Next and Experimental channels simultaneously, we'll do them one after the other. If we did want to speed up these publish workflows, we could paralellize by package instead of by release channel.
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
3 participants
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.
npm will sometimes fail if you try to concurrently publish two different versions of the same package, even if they use different dist tags.
So instead of publishing to the Next and Experimental channels simultaneously, we'll do them one after the other.
If we did want to speed up these publish workflows, we could parallelize by package instead of by release channel.