Skip to content
Merged
Changes from all commits
Commits
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
5 changes: 3 additions & 2 deletions default.json
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
"docker:enableMajor",
":rebaseStalePrs"
],
"minimumReleaseAge": "3 days",
"minimumReleaseAge": "12 hours",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep npm updates behind the 72-hour window

When this shared preset is used by npm/pnpm repos, this global age also applies to the non-major package rules that inherit automerge. I checked Renovate's minimumReleaseAge docs, which note that npm packages less than 72 hours old can still be unpublished and recommend 3 days; with 12 hours, Renovate can squash-merge a lockfile to a release that disappears before the npm unpublish window closes, breaking later installs or deploys. Please keep a 3-day package rule for npm/pnpm if other ecosystems need the shorter delay.

Useful? React with 👍 / 👎.

"prHourlyLimit": 0,
"prConcurrentLimit": 10,
"rebaseWhen": "behind-base-branch",
Expand All @@ -23,7 +23,7 @@
"osvVulnerabilityAlerts": true,
"packageRules": [
{
"description": "Auto-merge non-major updates once CI is green and stability delay clears.",
"description": "Auto-merge non-major updates once CI is green and the short stability delay clears.",
"matchUpdateTypes": ["minor", "patch", "pin", "digest"],
"automerge": true,
"automergeType": "pr",
Expand All @@ -45,6 +45,7 @@
{
"description": "Bundle all GitHub Actions updates into one PR.",
"matchManagers": ["github-actions"],
"matchUpdateTypes": ["minor", "patch", "pin", "digest"],
"groupName": "github-actions"
},
{
Expand Down