Skip to content

Commit

Permalink
chore: Upgrade to yarn 4.3.1 (microsoft#2148)
Browse files Browse the repository at this point in the history
## Summary:

Originally, I meant to just update the lock to resolve some CVEs. It
seems our lock is actually clean, so instead I'm updating yarn to the
latest version.

## Test Plan:

CI passes.
  • Loading branch information
Saadnajmi committed Jul 26, 2024
2 parents 67152e1 + 2592d27 commit 73cdf93
Show file tree
Hide file tree
Showing 5 changed files with 2,325 additions and 2,348 deletions.
893 changes: 0 additions & 893 deletions .yarn/releases/yarn-4.0.2.cjs

This file was deleted.

894 changes: 894 additions & 0 deletions .yarn/releases/yarn-4.3.1.cjs

Large diffs are not rendered by default.

5 changes: 3 additions & 2 deletions .yarnrc.yml
Original file line number Diff line number Diff line change
@@ -1,2 +1,3 @@
nodeLinker: "node-modules"
yarnPath: .yarn/releases/yarn-4.0.2.cjs
nodeLinker: node-modules

yarnPath: .yarn/releases/yarn-4.3.1.cjs
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -131,5 +131,5 @@
"shell-quote": "Versions prior to 1.7.3 have an RCE vulnerability. Should be removable once we upgrade CLI tools to ^8.0.0 with RN 0.69.",
"tough-cookie": "@definitelytyped/dtslint indirectly depends on this through an out-of-date library, and our particular use case doesn't need cookies"
},
"packageManager": "yarn@4.0.2"
"packageManager": "yarn@4.3.1"
}
Loading

0 comments on commit 73cdf93

Please sign in to comment.