Skip to content

ci(renovate): prHourlyLimit 1 with two runs a day caps Renovate at 2 PRs a day #9462

Open

Description

@waynesun09

Problem

Renovate opens at most 2 PRs a day here, and updates queue for weeks. 34 updates are waiting under "Rate-Limited" on the Dependency Dashboard (#2682). One example is sheeki03/tirith 0.5.0, released 2026-11-02 and not yet opened as a PR.

Two limits combine to cause this:

Limit Where Effect
"prHourlyLimit": 1 renovate.json 1 new PR per run
cron: "13 3,15 * * *" .github/workflows/renovate.yml 2 runs a day, so at most 2 new PRs a day
prConcurrentLimit not set, so Renovate's default of 10 applies renovate.json no new PRs while 10 Renovate PRs are open

The evidence:

What to change

Pick one or both:

  1. Raise the hourly cap. For example "prHourlyLimit": 4, or 0 for no hourly cap, relying on the concurrent limit instead.
  2. Set the concurrent cap explicitly, for example "prConcurrentLimit": 15. Also close or merge the PRs that have been open longest, so slots free up.

Out of scope

How to verify

After the change, the next scheduled runs open more than 2 PRs a day until the "Rate-Limited" list on #2682 shrinks.

Activity

  1. fullsend-ai-triage commented on Nov 13, 2026

    @fullsend-ai-triage

    🤖 Finished Triage · ✅ Success · Started 10:57 PM UTC · Completed 10:59 PM UTC

    Commit: b2945ba · View workflow run →

    Runtime: claude · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $0.12

  2. added
    triagedTriaged but awaiting human prioritization
    type/choreMaintenance and housekeeping tasks
    dependenciesPull requests that update a dependency file
    priority/lowNice to have, address when convenient
    on Nov 13, 2026
  3. fullsend-ai-triage commented on Nov 13, 2026

    @fullsend-ai-triage

    Triage confirms the diagnosis: renovate.json sets prHourlyLimit to 1 and leaves prConcurrentLimit unset (default 10), and the workflow cron fires twice a day. No open PR or duplicate issue addresses this; #9461 (tirith bump) is a separate item.

    Fix scope: the change is confined to renovate.json; the workflow cron does not need to change, so no workflow-file edits are needed. Suggested approach: raise prHourlyLimit and set prConcurrentLimit explicitly, choosing values that keep the review load manageable. Because the concurrent cap is already saturated, raising only the hourly limit will not help until some of the long-open Renovate PRs are merged or closed. That cleanup is a maintainer action and is not something the code change can do.

    Proposed verification: validate the config with Renovate's config validator, then confirm after merge that scheduled runs open more than 2 PRs a day until the Rate-Limited list on the dashboard shrinks.

    Note: the count of open Renovate PRs could not be independently re-verified during triage, so it is taken from the report.


    Labels: This is a Renovate/CI configuration chore affecting dependency updates, with low severity since updates are delayed rather than broken.


    Next steps:

    • /fs-code — agent creates a PR to implement this issue
    • /fs-code <your instruction> — agent implements with your specific guidance
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    component/ciCI pipelines and checksdependenciesPull requests that update a dependency filepriority/lowNice to have, address when convenienttriagedTriaged but awaiting human prioritizationtype/choreMaintenance and housekeeping tasks

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions