Migrate to yarn 4#12
Open
franklovefrank wants to merge 3 commits into
Open
Conversation
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
1 participant
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.
Why
Dependabot's corepack yarn install --mode=skip-build was failing with RequestError: getaddrinfo EAI_AGAIN classic.yarnpkg.com because four git-hosted fork dependencies have Yarn Classic yarn.lock files — when Yarn 4 repacks them in a clean clone (no .yarn/cache), it detects the missing __metadata key and tries to bootstrap Yarn Classic by downloading https://classic.yarnpkg.com/latest.js, which times out in the restricted network.
See #33420 for more context
What changed
This PR adds "packageManager": "yarn@4.x" to each fork and regenerates the yarn.lock