Skip to content

🔧 Move minimumReleaseAge to specific Renovate rule#159

Merged
IamPekka058 merged 2 commits into
mainfrom
chore/removeDefaultMinumumReleaseAge
May 5, 2026
Merged

🔧 Move minimumReleaseAge to specific Renovate rule#159
IamPekka058 merged 2 commits into
mainfrom
chore/removeDefaultMinumumReleaseAge

Conversation

@IamPekka058
Copy link
Copy Markdown
Member

This pull request updates the renovate-rubberduckcrew.json configuration to improve how dependencies are managed and automerged. The most important changes are focused on automerge rules and the handling of release age for updates.

Dependency update and automerge configuration:

  • Added a new rule to delay automerging of all updates (patch, minor, and major) until they are at least 3 days old, ensuring more time for review before merging.
  • Removed the global minimumReleaseAge setting and moved it into a specific update rule for better control and clarity.

@IamPekka058 IamPekka058 requested a review from Friedinger May 5, 2026 11:23
@IamPekka058 IamPekka058 added the 🔧 Configuration Changes to configuration files or settings label May 5, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 5, 2026

Warning

Rate limit exceeded

@IamPekka058 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 55 minutes and 54 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0304103d-2731-404b-8483-881de124c730

📥 Commits

Reviewing files that changed from the base of the PR and between cdfe080 and 8ff751c.

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

Walkthrough

This PR updates the Renovate configuration to add an explicit automerge rule for patch updates while maintaining the existing minimum release age constraint for all update types.

Changes

Renovate Patch Automerge Configuration

Layer / File(s) Summary
Patch Automerge Rule
configs/renovate/renovate-rubberduckcrew.json
A new packageRules entry is inserted to target patch updates only with automerge: true, positioned before the existing rule matching patch/minor/major with minimumReleaseAge: "3 days".
Formatting Adjustment
configs/renovate/renovate-rubberduckcrew.json
Minor formatting change near the vulnerabilityAlerts section closing.

Estimated Code Review Effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly Related PRs

Suggested Reviewers

  • Friedinger

Poem

🐰 A patch hops by with automerge so fast,
While three-day age checks make safety last,
Config rules dance in their JSON way—
No duck shall merge without proper delay! 🦆

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description check ✅ Passed The description accurately explains the changes: removing global minimumReleaseAge, adding a new rule with it for all update types, and improving automerge configuration clarity.
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.
Title check ✅ Passed The PR title uses an emoji and mentions moving minimumReleaseAge, which aligns with the core change of reorganizing the Renovate configuration rule. The title is specific and clear.

✏️ 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/removeDefaultMinumumReleaseAge

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.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@configs/renovate/renovate-rubberduckcrew.json`:
- Around line 21-22: The JSON object contains a trailing comma after the
"automerge": true entry which makes the file invalid; remove the trailing comma
following "automerge": true so the object closes with just }, ensuring the
Renovate config parses as valid JSON and no extra commas remain before the
closing brace.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 39b557be-1c5d-4f87-9d08-28ab5dd6b884

📥 Commits

Reviewing files that changed from the base of the PR and between ebbaa64 and cdfe080.

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

Comment thread configs/renovate/renovate-rubberduckcrew.json Outdated
@IamPekka058 IamPekka058 changed the title 🔧 Remove minimumReleaseAge from Renovate config 🔧 Move minimumReleaseAge to specific Renovate rule May 5, 2026
IamPekka058

This comment was marked as resolved.

@IamPekka058 IamPekka058 merged commit 5a0a828 into main May 5, 2026
3 checks passed
@IamPekka058 IamPekka058 deleted the chore/removeDefaultMinumumReleaseAge branch May 5, 2026 11:29
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