chore(deps): update dependency com.google.cloud:google-cloud-bigquerystorage-bom to v3.19.1

[renovate-bot]

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.google.cloud:google-cloud-bigquerystorage-bom	3.19.0 → 3.19.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

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

[dpebot]

/gcbrun

[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 upgrades the google-cloud-bigquerystorage-bom dependency to its v3.20.0-rc1 release candidate. This update incorporates a wide array of new features, crucial bug fixes, and performance optimizations, enhancing the client library's functionality and stability. It also ensures that the project benefits from the latest underlying dependency versions.

Highlights

• Dependency Upgrade: Updates the google-cloud-bigquerystorage-bom to v3.20.0-rc1, introducing a release candidate version with numerous enhancements and fixes.
• New Features: Introduces significant capabilities such as support for Arrow format in the Write API, integration of OpenTelemetry for metrics and tracing, and the ability to write Range values with JSONStreamWriter.
• Performance & Reliability: Includes improvements like optimized connection pool scaling, increased capacity for writing partitions in a single request, and refined retry mechanisms.

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 updates the com.google.cloud:google-cloud-bigquerystorage-bom dependency from version 3.19.0 to 3.20.0-rc1. My primary feedback is a caution against using a release candidate (-rc1) version. Although the Renovate configuration for this repository allows proposing unstable versions, pre-release versions can be unstable and are generally not recommended for inclusion in a main branch. It would be safer to wait for the stable release.

[gemini-code-assist]

This updates the dependency to a release candidate version (3.20.0-rc1). Release candidates are not considered stable and may contain bugs or breaking changes that will be fixed before the final release. It is highly recommended to wait for the stable release (3.20.0) to avoid potential instability in the project. Using pre-release versions should typically be limited to development or testing environments, not integrated into the main branch.

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[forking-renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[dpebot]

/gcbrun

[diegomarquezp]

/gcbrun