Skip to content

Update Renovate configuration for best practices (INT-356)#3

Merged
glaracuente merged 1 commit intomainfrom
chore/INT-356/renovate_min_age_pin_digests
May 5, 2026
Merged

Update Renovate configuration for best practices (INT-356)#3
glaracuente merged 1 commit intomainfrom
chore/INT-356/renovate_min_age_pin_digests

Conversation

@glaracuente
Copy link
Copy Markdown

what

  • Rename .github/renovate.json to .github/renovate.json5 to keep aligned with our other repos.
  • Switch from config:base to config:best-practices to keep aligned with our other repos, and enhance security on this repo in general.
  • Set minimumReleaseAge: 3 days globally so Renovate waits 3 days after any release before opening an upgrade PR. This applies to all managed dependency types.
  • Add github-actions to enabledManagers. We also want to make sure we enable pinDigests: true here, 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 minimumReleaseAge window 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

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 5, 2026

Warning

Rate limit exceeded

@glaracuente has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 26 minutes and 32 seconds before requesting another review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 53a3ea51-402e-4522-aeaf-67a1cb959211

📥 Commits

Reviewing files that changed from the base of the PR and between d6bddab and 22c428f.

📒 Files selected for processing (1)
  • .github/renovate.json5
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/INT-356/renovate_min_age_pin_digests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@glaracuente glaracuente merged commit a4123f5 into main May 5, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants