chore: Change bigquerystorage upgrade from chore to deps

[blakeli0]

deps update from bigquerystorage was incorrectly marked as chore(deps). This would cause the upgrade not show up in the release notes and also not trigger release please.

This is because the pattern /^com.google.cloud:google-cloud-bigquery is configured in renovate.json, which matches both bigquery and bigquerystorage. However, I believe the original intention is only for bigquery update in samples, not for bigquerystorage update.

Fixing the pattern so that the String must ends with bigquery.

[gemini-code-assist]

Summary of Changes

Hello @blakeli0, 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 refines the Renovate Bot configuration to ensure accurate categorization of dependency updates for Google Cloud libraries. The changes address a previous issue where bigquerystorage updates were being mislabeled due to an overly broad regular expression. By removing an incorrect configuration and making the bigquery regex more precise, this PR ensures that dependency updates are correctly identified and categorized, improving the clarity and accuracy of automated commit messages.

Highlights

• Renovate Configuration Refinement: Removed an outdated and potentially misleading matchPackageNames configuration block that was incorrectly categorizing bigquerystorage dependency updates.
• Precise Regex Matching: Modified the regular expression for google-cloud-bigquery to include an end-of-string anchor ($), ensuring that it exclusively matches google-cloud-bigquery and no longer inadvertently captures google-cloud-bigquerystorage.

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 correctly resolves an issue where Renovate was miscategorizing google-cloud-bigquerystorage dependency updates. By anchoring the regex for google-cloud-bigquery to the end of the string, the pattern is now specific and no longer incorrectly matches bigquerystorage. The removal of the now-superfluous package rule for bigquerystorage is also a good cleanup. The changes are accurate and effectively fix the problem.