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 to Yarn 3.1 #13856
Update to Yarn 3.1 #13856
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit ccea12e:
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/49331/ |
a60919b
to
eede874
Compare
Even if Yarn 3.1 is not stable yet, I'd like to merge this as soon as yarnpkg/berry#3610 is merged because Yarn 3.0 doesn't work on Node.js 17 (#13866 (comment)) |
eede874
to
c0a8ea9
Compare
c0a8ea9
to
1fab656
Compare
I don't see how the failure in https://app.circleci.com/pipelines/github/babel/babel/8286/workflows/96713762-dd27-4c39-9142-3fd3e490017c/jobs/49330 could be related (and it's consistent - I restarted it 3 times), but lets see if the last commit fixes it. |
The other CI e2e failures on CircleCI are caused by libraries not supporting Node.js 17 yet - they are not related to this PR. |
I'm marking this as "Fixes failing main" even if some e2e tests still fail (because CRA and |
This is mostly to test that Yarn 3.1.0 doesn't break us, before that it's released as stable. The first commit is #13858.
The constraints plugin has a breaking change: yarnpkg/berry#3584