chore: upgrade to Yarn 4.1.1 and Node 20 in CI #3934
Merged
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.
What is the previous behavior before this PR?
Yarn 3.2.2, which didn't support modern Node (see #3931).
CI used Node 14 and 16.
What is the new behavior after this PR?
Latest version of Yarn 4.1.1, which no longer requires checking in the Yarn binary to the repository.
Instead we require developers to run the command
corepack enable
(once per machine) beforeyarn
.Also requires developers to use Node 18+ (as required by Yarn 4).
CI now uses Node 20 and calls
corepack enable
.Fixes #3931