chore(deps): harden supply chain policy#5387
Open
jgoux wants to merge 3 commits into
Open
Conversation
bafac4b to
7d39a83
Compare
7d39a83 to
1d7f3f9
Compare
Coly010
approved these changes
May 29, 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
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.
What changed
blockExoticSubdeps: true.minimumReleaseAge: 0, because the current lockfile contains packages newer than pnpm v11's default 24-hour window.Context
Recent npm supply-chain incidents make dependency freshness delay and stricter lockfile verification worth encoding as repository policy. Dependabot now carries the 7-day cooldown policy, while pnpm release-age enforcement can be enabled in a follow-up once the current lockfile has aged enough. The stricter pnpm trust downgrade policy is intentionally left out for now because it needs more review before enforcement.