Skip to content

🔧 Set renovate minimum release age to 3 days#156

Merged
Friedinger merged 1 commit intomainfrom
config/minimum-release-age
Apr 21, 2026
Merged

🔧 Set renovate minimum release age to 3 days#156
Friedinger merged 1 commit intomainfrom
config/minimum-release-age

Conversation

@Friedinger
Copy link
Copy Markdown
Member

This pull request introduces a configuration update to the Renovate bot settings, specifically adding a minimum release age for dependency updates. This ensures that only packages released at least three days ago will be considered for updates, helping to avoid issues with unstable or quickly-patched releases.

Dependency update policy:

  • Added the "minimumReleaseAge": "3 days" setting to the Renovate configuration file (renovate-rubberduckcrew.json) to delay dependency updates until a release has been available for at least three days.

@Friedinger Friedinger requested a review from IamPekka058 April 20, 2026 19:50
@Friedinger Friedinger added the 🔧 Configuration Changes to configuration files or settings label Apr 20, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 20, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0b7cbc36-40d8-4834-819a-d6ca30ec7d98

📥 Commits

Reviewing files that changed from the base of the PR and between 77c9f87 and 8795deb.

📒 Files selected for processing (1)
  • configs/renovate/renovate-rubberduckcrew.json

Walkthrough

Added top-level minimumReleaseAge: "3 days" field to the Renovate configuration file, broadening the application of this setting globally across the configuration beyond its previous scope limited to a specific patch package rule.

Changes

Cohort / File(s) Summary
Renovate Configuration
configs/renovate/renovate-rubberduckcrew.json
Added top-level minimumReleaseAge field set to "3 days", expanding the minimum release age requirement to apply globally across the Renovate configuration instead of limiting it to patch updates only.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested reviewers

  • IamPekka058

Poem

🐰✨ A duck with care configures with grace,
Three days for release—a safer pace!
From patch-rules deep to the top it flies,
Guarding stability under spring skies! 🌱

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: adding a minimum release age setting of 3 days to the Renovate configuration.
Description check ✅ Passed The description clearly explains the change and its purpose: adding a minimum release age setting to prevent unstable releases.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ 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 config/minimum-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.

@Friedinger Friedinger merged commit 9359cf3 into main Apr 21, 2026
5 checks passed
@Friedinger Friedinger deleted the config/minimum-release-age branch April 21, 2026 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🔧 Configuration Changes to configuration files or settings

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants