From c0a1c0f93966fe33edd93fb53e5fafb0dcd80a9e Mon Sep 17 00:00:00 2001 From: Andrew Clark Date: Tue, 22 Oct 2019 11:44:24 -0700 Subject: [PATCH] Test React integration using `next` dist-tag (#9165) Instead of `canary`. React uses `next` to represent the next minor release. --- .circleci/config.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.circleci/config.yml b/.circleci/config.yml index 1bb2ef8cc4..e35413238a 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -41,11 +41,11 @@ commands: - run: name: Linting command: yarn lint - yarn_react_canary: + yarn_react_integration: steps: - run: - name: Upgrade to React Canary - command: yarn upgrade react@canary react-dom@canary -W --dev # upgrade (vs add) will skip re-building Next.js, which doesn't bundle React internals (so this is OK!) + name: Upgrade to most recent release in React's Next channel + command: yarn upgrade react@next react-dom@next -W --dev # upgrade (vs add) will skip re-building Next.js, which doesn't bundle React internals (so this is OK!) yarn_info: steps: - run: @@ -128,7 +128,7 @@ jobs: executor: node steps: - *attach_workspace - - yarn_react_canary + - yarn_react_integration - *persist_to_workspace test: parallelism: 3 -- GitLab