chore: Bump Yarn to 4.10.3 and configure NPM age gate
#3691
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.
Explanation
This bumps Yarn to the latest version (
4.10.3), which includes support for setting an age gate for NPM packages. It's set to 3 days following the security recommendations, meaning that packages must be at least 3 days old to be installed.References
MetaMask/metamask-module-template#270
Note
Upgrades Yarn to 4.10.3, adds a 3-day npm age gate with preapproved packages, and updates related configs and LavaMoat policy references.
yarnPathand rootpackageManagerto[email protected]in.yarnrc.yml,package.json, andyarn.config.cjs.npmMinimalAgeGate: 4320andnpmPreapprovedPackages(@metamask/*,@lavamoat/*) in.yarnrc.yml.policy.jsonto referencedepcheck>readdirp>picomatchinstead ofts-loader>micromatch>picomatchin relevant entries.Written by Cursor Bugbot for commit 635d8c1. This will update automatically on new commits. Configure here.