cherry-pick Free disk space for snapshot job and use correct requirements file (#36681)

[damccorm]

This is needed for the rerelease container job

---

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.

[damccorm]

R: @Amar3tto

One more PR to fix the ml containers on the postrelease branch

[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 streamlines the dependency management for Python SDK container images by consolidating requirements files and updating numerous package versions. These changes are essential for supporting the rerelease container job, ensuring that the build process uses up-to-date and correctly structured dependency lists, and potentially contributing to freeing up disk space as indicated by the cherry-pick title.

Highlights

• Requirements File Consolidation: The ml_image_requirements.txt files have been removed, and their functionality consolidated into base_image_requirements.txt across various Python versions (3.9, 3.10, 3.11, 3.12, 3.13).
• Dependency Updates: Numerous Python package dependencies have been updated to their latest versions within the base_image_requirements.txt files for Python 3.9, 3.10, 3.11, and 3.12.
• Build Process Alignment: The common.gradle build script has been updated to correctly reference the consolidated base_image_requirements.txt file, ensuring the build process uses the right set of dependencies.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/beam_Publish_Beam_SDK_Snapshots.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 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. ↩

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

[damccorm]

Note that failing tests are the same as #36677 (comment) so that is not an issue here.

@Amar3tto could you please take a look? I think this will fix https://github.com/apache/beam/actions/workflows/republish_released_docker_containers.yml

[damccorm]

@Amar3tto could you please take a look at this one?