Update Google BOM to 26.79.0#38021
Conversation
Summary of ChangesHello, 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 several Google Cloud Platform library dependencies to ensure compatibility and leverage the latest features and fixes. The changes were verified using the project's standard linkage check tools to ensure no new dependency conflicts were introduced. Highlights
🧠 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 AssistThe 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
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 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. Footnotes
|
66eca10 to
f7022b5
Compare
|
Looks like google cloud auth had breaking change, causing some integration test failures |
|
Restarted checks, let's see |
|
Assigning reviewers: R: @Abacn for label java. Note: If you would like to opt out of this review, comment Available commands:
The PR bot will only process comments in the main thread (not review comments). |
|
Merged when it wasn't green. Please don't! It looks like the same failures were still failing? |
|
It was green after rerun: https://github.com/apache/beam/actions/runs/23823214942 GitHub PR page "View details" shows all workflow run histories including failed (then retry succeeded) ones HEAD remains green after this PR merged. Still not fully understood why the auth error happened once |
Got it. I saw "24 out of 27 passed in the summary" then open it up and top result is a failure. Weird UI. Carry on! |
Used
bomupgrader.pyto update BOM and checked withbeam-linkage-check.sh origin/master update-google-bom ""Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
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, commentfixes #<ISSUE NUMBER>instead.CHANGES.mdwith noteworthy changes.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.