Migrate from Yarn Classic to Yarn Berry #2222
Merged
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
Kocal
force-pushed
the
yarn-berry
branch
4 times, most recently
from
9803ec4 to
f7b9c53
Compare
|
Turbo failures seems related. That appart, perfect ! |
|
Yeah I was just taking a break :) it should be fine now EDIT: if the CI wants to run 🥲 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Yarn 1.x is dead since 4 years now:
all new features and bug fixes are done on Yarn Berry:
I've adapted our CI, our building and testing scripts.
Updates on
src/**/assets/packages.jsonare simply dependencies alphabetical sorting.The
yarn.lockhas been re-generated to the new structure (but locked versions are still the same).