Fix bom upgrader and upgrade to latest

[damccorm]

There's a known BigTable issue in the previous bom version which this fixes. As part of this, I also fixed the bom upgrader script which was expecting spanner to be pinned (removed in 25518f0)

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[gemini-code-assist]

Summary of Changes

Hello @damccorm, 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 addresses a critical BigTable compatibility issue by updating the core Google Cloud Platform libraries BOM. Concurrently, it refines the automated BOM upgrader script to reflect current dependency pinning practices, ensuring smoother future updates and preventing errors related to outdated dependency expectations.

Highlights

• BigTable Issue Fix: Resolved a known BigTable issue by upgrading the Google Cloud Platform libraries BOM to a newer version.
• BOM Upgrader Script Fix: Corrected the bomupgrader script to no longer expect Spanner to be pinned, aligning with recent changes in dependency management.

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

Changelog

• buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy
  • Updated gax_version from 2.74.0 to 2.74.1.
  • Updated google_cloud_datastore_v1_proto_client from 2.33.3 to 2.34.0.
  • Updated google_cloud_platform_libraries_bom from 26.75.0 to 26.76.0.
  • Updated gax_version to 2.74.1.
  • Updated google_cloud_datastore_v1_proto_client to 2.34.0.
  • Updated google_cloud_platform_libraries_bom to 26.76.0.
• scripts/tools/bomupgrader.py
  • Removed google_cloud_spanner from the KNOWN_DEPS dictionary, as it is no longer expected to be pinned.
• sdks/java/container/license_scripts/dep_urls_java.yaml
  • Updated the libraries-bom version from 26.75.0 to 26.76.0.

Activity

• The pull request was opened by damccorm.
• Standard contribution checklist and CI status badges are present in the description, indicating initial setup for review.

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