prConcurrentLimit set inside a packageRule narrows the threshold but doesn't scope the counter #44410
Unanswered
Amine-Mike
asked this question in
Request Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate CLI
Which platform you running Renovate on?
GitLab (.com or self-hosted)
Which version of Renovate are you using?
43.253.2
Please tell us more about your question or problem
We tried to give different dependency groups independent concurrent-PR quotas
(e.g. "at most 2 open npm branches AND at most 2 open pep621/python branches,
independent of each other") using packageRules:
We expected this to behave like two independent buckets (up to 2 npm + up to 2
pep621 = up to 4 concurrent total, matching the global prConcurrentLimit).
Instead, once any 2 branches exist in the repo — regardless of manager — every
other branch whose matching rule also resolves to a limit of 2 gets permanently
blocked, even if none of the existing branches belong to that manager. In our
case, two npm branches were created first, and every subsequent pep621 (python)
dependency has been blocked from ever getting a branch, indefinitely.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions