Scoped prConcurrentLimit per packageRule (independent counters, not just a shared threshold)

[Amine-Mike]

Tell us more.

Today, prConcurrentLimit inside a packageRule only sets a lower threshold — it's still checked against the repo-wide count of all open Renovate branches/PRs, not a counter scoped to that rule.

Example:

{
  "prConcurrentLimit": 4,
  "packageRules": [
    { "matchManagers": ["npm"], "prConcurrentLimit": 2 },
    { "matchManagers": ["pep621"], "prConcurrentLimit": 2 }
  ]
}

Expected: 2 npm + 2 pep621 concurrently (4 total). Actual: once any 2 branches exist (e.g. both npm), every other rule with limit=2 is blocked — even branches from a totally different manager. One manager can permanently starve another.

Request: an opt-in way to scope prConcurrentLimit so the count only includes branches/PRs matching that same rule, giving true independent per-manager/per-group quotas.

This would be especially valuable for monorepos, where a single repo commonly spans multiple ecosystems/managers (npm, pep621, etc.) or multiple independent packages/workspaces. Without scoped limits, a noisy manager or workspace can starve out updates in other parts of the monorepo indefinitely, which is a real operational pain point as monorepo adoption grows.