Skip to content

Wait a bit before installing new package versions #8197

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 17, 2025
Merged

Wait a bit before installing new package versions #8197

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions renovate.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@
},
"automergeType": "branch",
"rebaseWhen": "conflicted",
"minimumReleaseAge": "7 days",
Copy link
Contributor

@BacLuc BacLuc Sep 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just as info: this is for everything, not just npm

Copy link
Member Author

@carlobeltrame carlobeltrame Sep 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, thanks for bringing it up. This is more or less on purpose. Even though the recent breaches have been on npm, other package managers and registries are not immune to such attacks.

"lockFileMaintenance": {
"enabled": true,
"schedule": ["on wednesday and thursday"]
Expand Down