ci(renovate): disable the per-hour PR creation throttle - #1091
Merged
Conversation
Renovate's prHourlyLimit defaults to 2, which throttles regular PR creation to ~2 per daily run. prConcurrentLimit already caps how many PRs stay open at once, and the once-daily schedule prevents bursts, so the hourly limit only slows working through the backlog. Setting it to 0 lets a run refill open PRs up to the concurrent limit. Signed-off-by: Jared Watts <jbw976@gmail.com>
haarchri
approved these changes
Jul 31, 2026
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
2 participants
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.
Description of your changes
Same fix as in crossplane/crossplane#7482, now here in crossplane-runtime
This PR sets Renovate's
prHourlyLimitto0, disabling the default cap of 2 PRs created per hour.Renovate docs entry for this field: https://docs.renovatebot.com/configuration-options/#prhourlylimit
prConcurrentLimit(5) already bounds how many Renovate PRs stay open at once, and our Renovate job runs on a once-daily schedule, so we are already protected that way. This hourly limit seemingly just slows us down, possibly limiting us to only 2 PRs per day (the one hour where our job runs once per day).Note that Security PRs already bypass both limits, so this only affects regular updates.
I have:
RunRenovate config-only change; the Renovate config validation workflow covers it../nix.sh flake checkto ensure this PR is ready for review.Added or updated unit tests.Config-only change.Added or updated e2e tests.Config-only change.Linked a PR or a docs tracking issue to document this change.Internal CI tooling, not user-facing.AddedRenovate reads this config frombackport release-x.ylabels to auto-backport this PR.mainfor all base branches; no per-branch backport needed.Followed the API promotion workflow if this PR introduces, removes, or promotes an API.No API change.