Skip to content

chore: have renovate hold PRs for 3 days after release#4788

Merged
escapedcat merged 1 commit into
masterfrom
chore/renovate-min-release-age
May 25, 2026
Merged

chore: have renovate hold PRs for 3 days after release#4788
escapedcat merged 1 commit into
masterfrom
chore/renovate-min-release-age

Conversation

@escapedcat

Copy link
Copy Markdown
Member

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.

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) <noreply@anthropic.com>
@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@escapedcat escapedcat merged commit 18e20b1 into master May 25, 2026
15 checks passed
@escapedcat escapedcat deleted the chore/renovate-min-release-age branch May 25, 2026 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant