chore: upgrade yarn to v3.8.7 #2098
Merged
+183
−183
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
SethFalco
force-pushed
the
yarn-upgrade
branch
8 times, most recently
from
f646541 to
2d3dc10
Compare
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.
Upgrade Yarn to v3.8.7.
We also switch the linker to
pnpmwhich should make that build step a little faster in theory, not that it was a notable issue before.I actually wanted to upgrade to v4, but we still support Node.js v16, which Yarn does not, so we'll remain on v3 for now. In the next major release of SVGO, we can change this.