Skip to content

renovate: Use weekly schedule instead of minimumReleaseAge#106

Merged
gursewak1997 merged 1 commit intobootc-dev:mainfrom
jeckersb:renovate-schedule
Feb 5, 2026
Merged

renovate: Use weekly schedule instead of minimumReleaseAge#106
gursewak1997 merged 1 commit intobootc-dev:mainfrom
jeckersb:renovate-schedule

Conversation

@jeckersb
Copy link
Copy Markdown
Contributor

@jeckersb jeckersb commented Feb 5, 2026

The minimumReleaseAge approach delays PRs but doesn't reduce their count -
if a package releases daily, we still get daily PRs, just 7 days late.

Switch to a schedule-based approach: all dependencies (except bcvk) are
updated only on Sundays (UTC). When Sunday arrives, Renovate proposes the
latest version available, skipping all intermediate releases from the week.

bcvk is excluded from the schedule and continues to update immediately.

Assisted-by: OpenCode (claude-opus-4-5@20251101)
Signed-off-by: John Eckersberg jeckersb@redhat.com

The minimumReleaseAge approach delays PRs but doesn't reduce their count -
if a package releases daily, we still get daily PRs, just 7 days late.

Switch to a schedule-based approach: all dependencies (except bcvk) are
updated only on Sundays (UTC). When Sunday arrives, Renovate proposes the
latest version available, skipping all intermediate releases from the week.

bcvk is excluded from the schedule and continues to update immediately.

Assisted-by: OpenCode (claude-opus-4-5@20251101)
Signed-off-by: John Eckersberg <jeckersb@redhat.com>
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @jeckersb, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the Renovate configuration to significantly reduce the volume of dependency update pull requests. By transitioning from a minimumReleaseAge delay to a weekly update schedule for most packages, it aims to consolidate updates and prevent excessive PR churn, while maintaining immediate updates for critical exceptions like bcvk.

Highlights

  • Dependency Update Strategy: Switched Renovate's dependency update mechanism from using minimumReleaseAge to a schedule-based approach.
  • Reduced PR Churn: Most dependencies will now be updated only once a week, on Sundays (UTC), consolidating multiple updates into a single pull request and skipping intermediate releases.
  • bcvk Exception: The bcvk package is explicitly excluded from the weekly schedule and will continue to receive immediate updates.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • renovate-shared-config.json
    • Replaced the global minimumReleaseAge: "7 days" rule with a new rule that schedules updates weekly on Sundays (UTC).
    • Modified the bcvk exception to use a negated matchPackageNames regex (!/^bcvk$/) within the new weekly schedule rule, ensuring it bypasses the schedule and updates immediately.
    • Updated inline comments to clarify the new scheduling logic and its benefits in reducing PR noise.
Activity
  • The author jeckersb initiated this pull request to change Renovate's update strategy.
  • The PR description indicates assistance from OpenCode (claude-opus-4-5@20251101).
  • The commit is signed off by John Eckersberg <jeckersb@redhat.com>.
  • The core change involves modifying renovate-shared-config.json to implement the new scheduling.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request refactors the Renovate configuration to reduce pull request churn by switching from a minimumReleaseAge strategy to a weekly schedule. This is a positive change, as it will consolidate multiple updates from a single week into one pull request. The implementation correctly uses a single rule with a schedule and a negated matchPackageNames to exclude the bcvk package, which will continue to update immediately. This new approach is more concise and maintainable than the previous two-rule system. The change is well-implemented and I have no suggestions for improvement.

Copy link
Copy Markdown
Contributor

@gursewak1997 gursewak1997 left a comment

Choose a reason for hiding this comment

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

lgtm

@gursewak1997 gursewak1997 merged commit 9f8a2bb into bootc-dev:main Feb 5, 2026
3 checks 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