renovate: Use weekly schedule instead of minimumReleaseAge#106
renovate: Use weekly schedule instead of minimumReleaseAge#106gursewak1997 merged 1 commit intobootc-dev:mainfrom
Conversation
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>
Summary of ChangesHello @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 Highlights
🧠 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
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
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.
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