Weekly update python dependencies 1766436327

[tarun-google]

Please add a meaningful description for your change here

---

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 @tarun-google, 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 systematically updates the Python dependencies for various container images, targeting Python versions 3.10 through 3.13 and covering base, machine learning, and GPU environments. The primary goal is to maintain up-to-date and secure dependencies, incorporating new libraries where necessary, and refining the dependency resolution logic in setup.py to accommodate Python 3.13's specific requirements.

Highlights

• Dependency Version Bumps: Numerous Python packages across py310, py311, py312, and py313 environments (base, ML, GPU) have been updated to their latest stable versions, ensuring the project uses up-to-date libraries.
• New Dependency Introductions: Several new dependencies, such as betterproto, distro, envoy_data_plane, google-cloud-monitoring, grpclib, h2, hpack, hyperframe, sniffio, and pydantic-settings, have been added to the requirements files to support new functionalities or address existing gaps.
• grpcio and protobuf Management: grpcio-tools has been added as a dependency, and grpcio-status was updated (including a specific downgrade in some requirements.txt files). The setup.py file now includes conditional dependency specifications for envoy-data-plane, protobuf, grpcio-status, and grpcio-tools to ensure compatibility across different Python versions, especially for Python 3.13.

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 36.33%. Comparing base (423a3c3) to head (0f81dfe).
⚠️ Report is 10 commits behind head on master.

Additional details and impacted files

@@              Coverage Diff              @@
##             master   #37170       +/-   ##
=============================================
- Coverage     55.14%   36.33%   -18.82%     
  Complexity     1676     1676               
=============================================
  Files          1067     1067               
  Lines        167116   167148       +32     
  Branches       1208     1208               
=============================================
- Hits          92163    60736    -31427     
- Misses        72771   104230    +31459     
  Partials       2182     2182               

Flag	Coverage Δ
python	40.61% <ø> (-40.16%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.