chore: wait 7 days before adopting new dependency releases - #14
Merged
Conversation
Both dependabot and pnpm now skip versions published in the last week, so a pulled or compromised release does not land in the lockfile.
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
1 participant
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
Both dependency paths now skip versions published less than 7 days ago.
.github/dependabot.yml:cooldown.default-days: 7on the npm entry, so the weekly grouped PR only picks up releases that are at least a week old..npmrc(new file):minimum-release-age=10080(minutes), so a manualpnpm addorpnpm updateresolves the same way.The
github-actionsentry is unchanged.Why
A package that gets compromised or pulled is usually caught within a few days of the release. Waiting a week means those versions never reach the lockfile in the first place.