chore: set yarn npmMinimalAgeGate#2022
Merged
Merged
Conversation
- Updated yarnPath in .yarnrc.yml to point to the new Yarn version 4.13.0. - Changed packageManager in package.json to reflect the updated Yarn version. - Removed old Yarn versions (4.5.1 and 1.22.18) from the releases directory. - Added new Yarn version (4.13.0) to the releases directory. - Set npmMinimalAgeGate to 3 days in .yarnrc.yml for package management optimization.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
brandon-pereira
changed the title
brandon-pereira
changed the title
brandon-pereira
changed the title
Contributor
Knip - Unused Code Analysis⚪ No changes detected (1 issues on both main and PR) What is this?Knip finds unused files, dependencies, and exports in your codebase. Run |
Contributor
PR ReviewThis is a clean, focused security PR. Changes are minimal and well-scoped.
Main concern: Validate the |
Contributor
E2E Test Results✅ All tests passed • 116 passed • 3 skipped • 1064s
Tests ran across 4 shards in parallel. |
pulpdrew
approved these changes
Mar 31, 2026
knudtty
pushed a commit
that referenced
this pull request
Apr 16, 2026
## Summary In response to the recent [axios supply chain attack](https://www.stepsecurity.io/blog/axios-compromised-on-npm-malicious-versions-drop-remote-access-trojan), we are tightening package management controls to reduce our exposure to malicious or compromised npm packages. **Changes:** - Updated `yarnPath` in `.yarnrc.yml` to point to Yarn 4.13.0 - Updated `packageManager` in `package.json` to reflect Yarn 4.13.0 - Removed old Yarn releases (4.5.1 and 1.22.18) from the `releases/` directory - Added Yarn 4.13.0 to the `releases/` directory - Set `npmMinimalAgeGate: 7` in `.yarnrc.yml` — Yarn will now block installation of any package version published less than 7 days ago, providing a buffer against freshly-injected malicious releases ### How to test locally or on Vercel 1. Pull this branch and run `yarn --version` — confirm it outputs `4.13.0`. 2. Run `yarn install` and verify it completes without errors. 3. Attempt to add a package version published within the last 7 days (e.g. a freshly released patch) and confirm Yarn rejects it with an age gate error. 4. Add a package version older than 7 days and confirm it installs successfully. 5. Confirm the old Yarn release files (`4.5.1`, `1.22.18`) are no longer present in `releases/`. ### References - Blog post: [axios compromised on npm — malicious versions drop remote access trojan](https://www.stepsecurity.io/blog/axios-compromised-on-npm-malicious-versions-drop-remote-access-trojan)
Copilot AI
pushed a commit
that referenced
this pull request
Apr 20, 2026
## Summary In response to the recent [axios supply chain attack](https://www.stepsecurity.io/blog/axios-compromised-on-npm-malicious-versions-drop-remote-access-trojan), we are tightening package management controls to reduce our exposure to malicious or compromised npm packages. **Changes:** - Updated `yarnPath` in `.yarnrc.yml` to point to Yarn 4.13.0 - Updated `packageManager` in `package.json` to reflect Yarn 4.13.0 - Removed old Yarn releases (4.5.1 and 1.22.18) from the `releases/` directory - Added Yarn 4.13.0 to the `releases/` directory - Set `npmMinimalAgeGate: 7` in `.yarnrc.yml` — Yarn will now block installation of any package version published less than 7 days ago, providing a buffer against freshly-injected malicious releases ### How to test locally or on Vercel 1. Pull this branch and run `yarn --version` — confirm it outputs `4.13.0`. 2. Run `yarn install` and verify it completes without errors. 3. Attempt to add a package version published within the last 7 days (e.g. a freshly released patch) and confirm Yarn rejects it with an age gate error. 4. Add a package version older than 7 days and confirm it installs successfully. 5. Confirm the old Yarn release files (`4.5.1`, `1.22.18`) are no longer present in `releases/`. ### References - Blog post: [axios compromised on npm — malicious versions drop remote access trojan](https://www.stepsecurity.io/blog/axios-compromised-on-npm-malicious-versions-drop-remote-access-trojan) Co-authored-by: peter-leonov-ch <209667683+peter-leonov-ch@users.noreply.github.com>
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.
Summary
In response to the recent axios supply chain attack, we are tightening package management controls to reduce our exposure to malicious or compromised npm packages.
Changes:
yarnPathin.yarnrc.ymlto point to Yarn 4.13.0packageManagerinpackage.jsonto reflect Yarn 4.13.0releases/directoryreleases/directorynpmMinimalAgeGate: 7in.yarnrc.yml— Yarn will now block installation of any package version published less than 7 days ago, providing a buffer against freshly-injected malicious releasesHow to test locally or on Vercel
yarn --version— confirm it outputs4.13.0.yarn installand verify it completes without errors.4.5.1,1.22.18) are no longer present inreleases/.References