[CI] Publish to release channels sequentially (#20827)
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.
Andrew Clark committed
Feb 16, 2021 at 00:04 UTC
6f8843837c4aec94d362560a021c3722d260f49f
1 file changed
+10
-2
.circleci/config.yml
+10
-2
@@ -553,7 +553,11 @@ workflows:
553
- publish_prerelease:
554
name: Publish to Experimental channel
555
requires:
556
- - setup
556
+ # NOTE: Intentionally running these jobs sequentially because npm
557
+ # will sometimes fail if you try to concurrently publish two
558
+ # different versions of the same package, even if they use different
559
+ # dist tags.
560
+ - Publish to Next channel
561
commit_sha: << pipeline.parameters.prerelease_commit_sha >>
562
release_channel: experimental
563
dist_tag: experimental
@@ -581,7 +585,11 @@ workflows:
585
- publish_prerelease:
586
name: Publish to Experimental channel
587
requires:
584
- - setup
588
+ # NOTE: Intentionally running these jobs sequentially because npm
589
+ # will sometimes fail if you try to concurrently publish two
590
+ # different versions of the same package, even if they use different
591
+ # dist tags.
592
+ - Publish to Next channel
593
commit_sha: master
594
release_channel: experimental
595
dist_tag: experimental