renovate: Add 1 week minimumReleaseAge for dependency updates

[cgwalters]

Reduce PR noise from rapidly-updating dependencies by waiting 1 week before proposing updates. Analysis showed some packages (e.g., opencode-ai) had 7 updates in 8 days, creating excessive churn.

Exceptions can be added for packages that should bypass the waiting period, such as our own projects (bcvk) or critical dependencies.

Assisted-by: OpenCode (Claude Sonnet 4)

[gemini-code-assist]

Summary of Changes

Hello @cgwalters, I'm Gemini Code Assist¹! 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 modifies the Renovate configuration to implement a strategy for managing dependency updates more efficiently. By introducing a default waiting period, it aims to significantly reduce the volume of pull requests generated by rapidly updating dependencies, thereby decreasing development team overhead and improving overall stability.

Highlights

• Renovate Configuration Update: Introduced a default 'minimumReleaseAge' of 7 days for all dependency updates to reduce PR noise and ensure stability.
• Dependency Update Exceptions: Added an exception rule for 'bcvk' packages, allowing them to be updated immediately without the 7-day waiting period.

🧠 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.

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a minimumReleaseAge of one week for all dependencies to reduce noise from frequent updates, which is a great improvement for stability and reducing churn. It also correctly adds an exception for bcvk packages to allow immediate updates. I've added one suggestion to make the package matching pattern for the exception more specific to prevent potential future conflicts.

[gemini-code-assist]

The current pattern ["bcvk"] will match any package name containing "bcvk" as a substring, which could unintentionally match unrelated packages. To make this rule more specific and prevent future issues, it's better to anchor the pattern to match only at the beginning of the package name.

If your packages are named like bcvk-cli, the suggested pattern ^bcvk is more precise. If they are scoped like @bcvk/core, you should use ^@bcvk/.

Suggested change

	"matchPackagePatterns": ["bcvk"],
	"matchPackagePatterns": ["^bcvk"],

[gursewak1997]

Looks like the validation is failing because matchPackagePatterns triggers a migration suggestion, and --strict mode treats this as an error.
Fix: Use matchPackageNames with regex delimiters or remove --strict

[gursewak1997]

Just need -s in commit command but lgtm