chore(config): migrate Renovate config

[renovate-bot]

The Renovate config in this repository needs migrating. Typically this is because one or more configuration options you are using have been renamed.

You don't need to merge this PR right away, because Renovate will continue to migrate these fields internally each time it runs. But later some of these fields may be fully deprecated and the migrations removed. So it's a good idea to merge this migration PR soon.

🔕 Ignore: Close this PR and you won't be reminded about config migration again, but one day your current config may no longer be valid.

❓ Got questions? Does something look wrong to you? Please don't hesitate to request help here.

---

This PR was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Summary of Changes

Hello @renovate-bot, 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 performs an automated migration of the Renovate configuration file (renovate.json). The primary goal is to update deprecated configuration options, such as fileMatch and matchManagers, to their current recommended forms. This ensures the configuration remains valid and functional as Renovate evolves, preventing potential issues when older syntax is eventually removed.

Highlights

• Renovate Configuration Migration: This pull request migrates the Renovate configuration by updating deprecated fields to their new equivalents, ensuring future compatibility and preventing potential issues when older syntax is fully removed.
• Renaming of fileMatch to managerFilePatterns: The fileMatch property within custom manager definitions has been renamed to managerFilePatterns and its values are now encapsulated in regex literal syntax (e.g., /pattern/).
• Update to matchManagers Property: The matchManagers property in a package rule has been updated from regex to custom.regex to reflect the current naming convention for custom regex managers.

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, generated by Renovate Bot, migrates the Renovate configuration to use newer fields like managerFilePatterns and custom.regex. The migration is generally correct and follows Renovate's new schema. However, I've identified a few pre-existing but now-surfaced issues in the regular expressions for file matching where a literal dot . in a directory name or file extension was not escaped. This could lead to incorrect file matching. I've provided suggestions to fix these patterns for improved correctness.

[gemini-code-assist]

The dots . in the file path .kokoro and file extension .cfg are special characters in regular expressions that match any character. To match literal dots, they should be escaped with a backslash (\.). This ensures the pattern only matches files in the .kokoro directory with a .cfg extension.

Suggested change

	"/^.kokoro/presubmit/graalvm-native.*.cfg$/"
	"/^\.kokoro/presubmit/graalvm-native.*\.cfg$/"

[gemini-code-assist]

The dot . in the file path .cloudbuild is a special character in regular expressions that matches any character. To match a literal dot, it should be escaped with a backslash (\.). This ensures the pattern only matches files in the .cloudbuild directory.

        "/^\.cloudbuild/*/

[gemini-code-assist]

The dot . in the file path .cloudbuild is a special character in regular expressions that matches any character. To match a literal dot, it should be escaped with a backslash (\.). This ensures the pattern only matches files in the .cloudbuild directory. Another pattern in this file for the same directory already does this correctly.

        "/^\.cloudbuild/library_generation/library_generation.*\.Dockerfile$/"