Repository navigation
v0.3.0
What's New
Rate Limiting & Caching
This release adds rate limiting and caching to prevent API failures when processing repositories with many commits between releases.
New Features:
- Concurrency control - Batches API requests (10 concurrent by default) using p-limit
- Automatic throttling - Handles GitHub's 429 rate limit responses with exponential backoff
- Persistent caching - Caches commit-to-PR mappings using @actions/cache for incremental updates
New Action Inputs:
concurrency-limit(default:10) - Maximum concurrent API requestsenable-cache(default:true) - Toggle PR caching
Performance Improvements:
| Scenario | Before | After |
|---|---|---|
| First run (500 commits) | 500 parallel calls → rate limited | Batched requests with throttling |
| Subsequent run (10 new) | 510 calls | 10 calls (rest cached) |
| No new commits | 500+ calls | 0 PR fetches (all cached) |