Skip to content

Conversation

@renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Jan 20, 2026

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.google.cloud:libraries-bom (source) 26.73.026.74.0 age adoption passing confidence

Release Notes

googleapis/java-cloud-bom (com.google.cloud:libraries-bom)

v26.74.0

Dependencies
  • update dependency com.google.cloud:first-party-dependencies to v3.55.1 (#​7337) (4e48025)
  • update dependency com.google.cloud:gapic-libraries-bom to v1.76.0 (#​7338) (a830b68)
  • update dependency com.google.cloud:google-cloud-bigquery to v2.57.2 (#​7340) (cd04436)
  • update dependency com.google.cloud:google-cloud-bigquerystorage-bom to v3.19.1 (#​7341) (6231057)
  • update dependency com.google.cloud:google-cloud-bigtable-bom to v2.71.0 (#​7328) (1c5b71d)
  • update dependency com.google.cloud:google-cloud-datastore-bom to v2.33.2 (#​7342) (52a1601)
  • update dependency com.google.cloud:google-cloud-firestore-bom to v3.35.0 (#​7317) (adc3c75)
  • update dependency com.google.cloud:google-cloud-firestore-bom to v3.35.1 (#​7348) (639da59)
  • update dependency com.google.cloud:google-cloud-logging-bom to v3.23.10 (#​7343) (f515976)
  • update dependency com.google.cloud:google-cloud-logging-logback to v0.132.21-alpha (#​7344) (d8a8d13)
  • update dependency com.google.cloud:google-cloud-nio to v0.128.10 (2c64e8c)
  • update dependency com.google.cloud:google-cloud-pubsub-bom to v1.145.0 (#​7324) (697e3d5)
  • update dependency com.google.cloud:google-cloud-pubsublite-bom to v1.15.21 (#​7346) (216e67c)
  • update dependency com.google.cloud:google-cloud-spanner-bom to v6.107.0 (#​7325) (fe85be2)
  • update dependency com.google.cloud:google-cloud-spanner-jdbc to v2.35.0 (#​7326) (d2a7690)
  • update dependency com.google.cloud:google-cloud-storage-bom to v2.62.0 (#​7320) (c5f487e)

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.

@renovate-bot renovate-bot requested review from a team as code owners January 20, 2026 04:03
@product-auto-label product-auto-label bot added size: xs Pull request size is extra small. api: bigquery Issues related to the googleapis/java-bigquery API. labels Jan 20, 2026
@dpebot
Copy link

dpebot commented Jan 20, 2026

/gcbrun

@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jan 20, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @renovate-bot, 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 updates the Google Cloud Libraries Bill of Materials (BOM) to its latest stable version. This ensures that the project benefits from the most recent bug fixes, performance enhancements, and new features across various Google Cloud client libraries, maintaining compatibility and leveraging the latest improvements provided by Google.

Highlights

  • Dependency Update: The com.google.cloud:libraries-bom dependency has been updated from version 26.73.0 to 26.74.0.
  • Sub-dependency Upgrades: This BOM update includes several underlying Google Cloud client library dependencies, such as first-party-dependencies, gapic-libraries-bom, and specific service BOMS like BigQuery, Firestore, Pub/Sub, and Spanner, bringing them to their latest versions.

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

@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jan 20, 2026
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the com.google.cloud:libraries-bom dependency to version 26.74.0. The update is straightforward and helps keep dependencies current. During the review, I identified a related issue in samples/snippets/pom.xml where a dependency, google-cloud-bigtable, has a hardcoded version. This practice overrides the version managed by the BOM and can lead to inconsistencies. With this update, the hardcoded version is now older than the one provided by the new BOM. I've left a comment on the relevant change with more details. It would be beneficial to address this in a follow-up to ensure consistent dependency management.

<groupId>com.google.cloud</groupId>
<artifactId>libraries-bom</artifactId>
<version>26.73.0</version>
<version>26.74.0</version>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While this BOM update is beneficial, it highlights a pre-existing dependency management issue within this file. The google-cloud-bigtable dependency (lines 110-115) has its version hardcoded to 2.62.0. This new libraries-bom version 26.74.0 provides google-cloud-bigtable at version 2.71.0.

Pinning the version overrides the version provided by the BOM, which can lead to dependency conflicts and negates the purpose of using a BOM. It is recommended to remove the <version>2.62.0</version> line for google-cloud-bigtable to allow the BOM to manage its version. This should be addressed in a follow-up change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: bigquery Issues related to the googleapis/java-bigquery API. size: xs Pull request size is extra small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants