ci: cap release-please search depth to spare the shared PAT rate limit - #14

What & why

release-please is failing with:

release search depth: 400
Error: release-please failed: ... API rate limit already exceeded for user ID 85048617.

85048617 is the shared org PAT user. The reusable workflow called release-please-action with only token, leaving release-search-depth (400) and commit-search-depth (500) at their defaults. release-please re-runs on every push to master across all 12 forks, all authenticating as that same PAT, so each run pages back through hundreds of releases/commits and a burst of merges (a night of Renovate automerges, or a run of manual merges) exhausts the user's ~5000/hr API budget.

The rate limit itself is transient and resets hourly — release-please recovers on the next push/dispatch, nothing is lost. This change is the durable fix so it stops recurring.

Change

uses: googleapis/release-please-action@…  # v5.0.0
with:
  token: ${{ secrets.PAT }}
+ release-search-depth: 40
+ commit-search-depth: 250

The forks are single-package manifests with single-digit release counts and a monthly release cadence, so 40/250 sit well above real history — this cuts ~10× off the release-search paging while staying far above any realistic commits-since-last-release, so no changelog entries are missed.

Rollout

Reusable-workflow change; forks pick it up when their @<sha> digest pin to this repo bumps (Renovate handles those digest updates). No fork edits needed.

Type of change

• fix / feat / perf — consumer-facing
• deps — dependency update
• chore / ci / build / docs / test / refactor — maintenance (ci)

Checklist

• Commits follow Conventional Commits (commitlint passes)
• Workflow YAML validated
• No behavior change beyond bounding the release/commit search window

Generated by Claude Code