add upgrade gcp bom workflow

[derrickaw]

1. add workflow to create PR to upgrade gcp bom if newer version exists weekly
2. https://github.com/apache/beam/actions/runs/26528828786

---

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, 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 introduces a new utility script designed to automate the monitoring of Google Cloud Platform libraries BOM versions. By comparing the latest available version from Maven Central against the version currently defined in the project's Gradle configuration, the script provides a mechanism to trigger alerts or workflows when an upgrade is required.

Highlights

• New Automation Script: Added a Python script to check for updates to the Google Cloud Platform libraries BOM.
• CI Integration: The script exports GITHUB_OUTPUT variables to facilitate automated version upgrade checks in CI workflows.

New Features

🧠 You can now enable Memory (public preview) 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.

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/README.md
  • .github/workflows/beam_Upgrade_GCP_BOM.yml

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 the 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 counterproductive. 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.

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 introduces a new Python script, gcp_bom_upgrade_check.py, designed to compare the latest Google Cloud Platform libraries BOM version from Maven Central with the version currently defined in the project's Gradle build configuration. The review comments point out several opportunities to improve the script's robustness: adding a timeout to the network request to prevent hanging, resolving the file path dynamically to allow execution from directories other than the repository root, and parsing version strings more defensively to handle non-integer suffixes safely.

[derrickaw]

assign set of reviewers

[github-actions]

Assigning reviewers:

R: @Abacn for label build.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[github-actions]

Reminder, please take a look at this pr: @Abacn

[Abacn]

This is currently handled by release manager as a post-release task

Based on my experience there is a half-half probability the tool needs modification each time it's invoked therefore I personally thought maintain an automated workflow might not worth it

[derrickaw]

This is currently handled by release manager as a post-release task

Based on my experience there is a half-half probability the tool needs modification each time it's invoked therefore I personally thought maintain an automated workflow might not worth it

It reduces the toil of running the tool and creating a PR etc. If all tests pass great, but if something doesn't work, then modifications should be minor but the user doesn't need to run the tool etc.

The tool itself needs modification?

Thoughts? Thanks.

[Abacn]

It reduces the toll of running the tool and creating a PR etc.

It doesn't. Currently the script simply print one line

if should_upgrade:
        print("A newer version of libraries-bom is available. Upgrade needed.")
    else:
        print("libraries-bom is up-to-date.")

maintainer need to go to workflow page, check log to get information. I feel it's same or mouse click than click https://mvnrepository.com/artifact/com.google.cloud/libraries-bom manually

sorry, I see there are following steps in github action yaml

[github-actions]

Reminder, please take a look at this pr: @Abacn

[damccorm]

What are next steps here @Abacn @derrickaw ?

[damccorm]

Rather than being an output, should this just run as part of the main bomupgrader script (optionally)?

[derrickaw]

updated, thanks

[github-actions]

Assigning new set of reviewers because Pr has gone too long without review. If you would like to opt out of this review, comment assign to next reviewer:

R: @damccorm for label build.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

[damccorm]

waiting on author

[damccorm]

Today we only update this right after releases - https://github.com/apache/beam/blob/master/contributor-docs/release-guide.md#update-the-java-bom - this is somewhat intentional since BOM upgrades tend to be:

1. Higher risk
2. Lower urgency (rarely are features blocked on this)

I think we probably want to keep this behavior.

We could probably do something like what we do for Python dependencies - https://github.com/apache/beam/blob/master/contributor-docs/release-guide.md#update-python-dependencies

At that point, we'd need to:

1. Add logic like

   beam/.github/workflows/update_python_dependencies.yml

   Line 87 in 63bcd3d

   echo "Exiting early. We only update dependencies the week after we cut the release"

   to this file
2. Update the release guide to have instructions similar to https://github.com/apache/beam/blob/master/contributor-docs/release-guide.md#update-python-dependencies

[derrickaw]

Today we only update this right after releases - https://github.com/apache/beam/blob/master/contributor-docs/release-guide.md#update-the-java-bom - this is somewhat intentional since BOM upgrades tend to be:

1. Higher risk
2. Lower urgency (rarely are features blocked on this)

I think we probably want to keep this behavior.

I knew about the timing, but if I understand the flow of things some package versions that have vulnerabilities are dependent on this BOM being updated. So the main drivers for this workflow are consistently having a weekly upgrade to minimize vulnerabilities, having a process in place so that we don't forget to do the upgrade, and having a workflow if we wanted to at any given point in time just run it and have a new PR ready to go without having to do anything locally.

I will go in the direction you suggest below, but I think in the future we should consider completing this upgrade more often.

We could probably do something like what we do for Python dependencies - https://github.com/apache/beam/blob/master/contributor-docs/release-guide.md#update-python-dependencies

At that point, we'd need to:

1. Add logic like

   beam/.github/workflows/update_python_dependencies.yml

   Line 87 in 63bcd3d

   echo "Exiting early. We only update dependencies the week after we cut the release"

   
   to this file
2. Update the release guide to have instructions similar to https://github.com/apache/beam/blob/master/contributor-docs/release-guide.md#update-python-dependencies

Ok, updated. Thanks.