Upgrade yarn#11942
Merged
Merged
Conversation
Member
|
|
Contributor
Author
|
The global yarn version matters, apparently. Looking to see if that's easily fixed. |
Contributor
Author
|
Figured it out; we had to use @bduffany does this work for you now? |
bduffany
approved these changes
Apr 21, 2026
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
2 participants
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 from yarn v1 to yarn v4. yarn v1 does not allow us to upgrade minor versions of dependencies, only patch versions, and this behavior is incorrect (overly restrictive) and pins us to versions of dependencies with security vulnerabilities.