Skip to content

chore: add minReleaseAge to Renovate conf (INT-356)#21

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

chore: add minReleaseAge to Renovate conf (INT-356)#21
glaracuente merged 1 commit intomainfrom
chore/INT-356/renovate_min_release_age

Conversation

@glaracuente
Copy link
Copy Markdown
Contributor

@glaracuente glaracuente commented May 5, 2026

what

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.

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.

references

Summary by CodeRabbit

  • Chores
    • Updated configuration to apply a 3-day minimum waiting period before dependency updates are considered.

@glaracuente glaracuente requested a review from a team as a code owner May 5, 2026 13:40
@glaracuente glaracuente requested a review from dudymas May 5, 2026 13:40
@glaracuente glaracuente changed the title chore: add minReleaseAge to Renovate (INT-356) chore: add minReleaseAge to Renovate conf (INT-356) May 5, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 5, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8de7842b-aa52-48a5-818d-9c8e1f723fa5

📥 Commits

Reviewing files that changed from the base of the PR and between bdd3129 and 1568758.

📒 Files selected for processing (1)
  • .github/renovate.json5

📝 Walkthrough

Walkthrough

This PR modifies the Renovate configuration file (.github/renovate.json5) by adding a single parameter: "minimumReleaseAge": "3 days". This parameter establishes a minimum age threshold that newly released dependencies must meet before becoming eligible for automatic updates. The change affects dependency update eligibility timing without modifying other functional configuration elements such as managers, schedules, or package rules.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: adding minimumReleaseAge to Renovate configuration, with a concise reference to the issue identifier.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/INT-356/renovate_min_release_age

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 6b758ba into main May 5, 2026
5 checks passed
@glaracuente glaracuente deleted the chore/INT-356/renovate_min_release_age branch May 5, 2026 13:44
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