Update Renovate configuration for best practices (INT-356)#3
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
what
.github/renovate.jsonto.github/renovate.json5to keep aligned with our other repos.config:basetoconfig:best-practicesto keep aligned with our other repos, and enhance security on this repo in general.minimumReleaseAge:3 daysglobally so Renovate waits 3 days after any release before opening an upgrade PR. This applies to all managed dependency types.github-actionsto enabledManagers. We also want to make sure we enablepinDigests: truehere, but that is already handled since we use config:best-practices, which includes this. Renovate will now track workflow dependencies and pin them to immutable SHA digests instead of mutable version tags. We are already doing this in practice, but this enforces it in a maintainable way.why
The
minimumReleaseAgewindow gives the community time to discover and report bugs or vulnerabilities in newly published releases before we adopt them. Without it, Renovate could open a PR for a release within minutes of it being published — before any post-release issues are known.Pinning GitHub Actions to SHA digests removes a supply chain attack vector: a compromised or malicious actor could rewrite a version tag (e.g. v4) to point at different code without any visible change to our workflow files. A pinned digest is immutable and tied to a specific commit. Renovate's digest update PRs will keep those pins current over time.
references