Add minReleaseAge to pnpm settings to reduce likelihood of supply chain compromises#5798
Merged
rtibbles merged 2 commits intolearningequality:unstablefrom Apr 1, 2026
Merged
Conversation
bjester
force-pushed
the
min-release-age
branch
from
0be6800 to
642cc26
Compare
rtibbles
approved these changes
Apr 1, 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.
Summary
minimumReleaseAgeshould reduce likelihood of supply chain compromisesminimumReleaseAgeto 1 week to match dependabotpnpmsince the feature needs at least 10.16.0References
https://nesbitt.io/2026/03/04/package-managers-need-to-cool-down.html
Reviewer guidance
Can you run
pnpm install?