From 2b0023123e70e39538a03a6760da2d67a666ebad Mon Sep 17 00:00:00 2001 From: escapedcat Date: Mon, 25 May 2026 12:49:43 +0200 Subject: [PATCH] chore: have renovate hold PRs for 3 days after release Recent renovate PRs went red because freshly-published versions weren't fully propagated on the npm registry / CDN. `minimumReleaseAge` delays PRs until the version is at least three days old, and `internalChecksFilter: "strict"` suppresses the PR entirely until that window passes rather than opening it and blocking merge. Co-Authored-By: Claude Opus 4.7 (1M context) --- package.json | 2 ++ 1 file changed, 2 insertions(+) diff --git a/package.json b/package.json index dcd4996047..5f7364bc03 100644 --- a/package.json +++ b/package.json @@ -88,6 +88,8 @@ "renovate": { "rangeStrategy": "update-lockfile", "rebaseWhen": "behind-base-branch", + "minimumReleaseAge": "3 days", + "internalChecksFilter": "strict", "ignorePaths": [ "**/fixtures/**/package.json" ],