Skip to content

Bump cryptography from 47.0.0 to 48.0.1 in Python container images#39204

Open
shahar1 wants to merge 2 commits into
apache:masterfrom
shahar1:bump-cryptography-4801
Open

Bump cryptography from 47.0.0 to 48.0.1 in Python container images#39204
shahar1 wants to merge 2 commits into
apache:masterfrom
shahar1:bump-cryptography-4801

Conversation

@shahar1

@shahar1 shahar1 commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Bumps cryptography from 47.0.0 to 48.0.1 across all Python container requirements files (base, ML, and GPU images), keeping the container images on the same version. Supersedes #38973 and #39015, which each cover a single container directory.

Verified pyOpenSSL==26.2.0 (the only pinned dependent) accepts cryptography<49, and all affected containers run Python >=3.10, satisfying cryptography 48's Python >=3.9 requirement.


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.

🤖 Generated with Claude Code

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 standardizes the 'cryptography' library version across all base, ML, and GPU Python container images. By bumping the version to 48.0.1, the project ensures security and feature parity across its containerized environments while maintaining compatibility with existing dependencies.

Highlights

  • Dependency Update: Updated the 'cryptography' library from version 47.0.0 to 48.0.1 across all Python container requirement files.
  • Compatibility Verification: Confirmed that pyOpenSSL 26.2.0 is compatible with the new version and that all target containers meet the Python 3.9+ requirement.
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.

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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the cryptography dependency from version 47.0.0 to 48.0.1 across various Python container base and GPU image requirements files, spanning Python versions 3.10 through 3.14. There are no review comments, and I have no additional feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Assigning reviewers:

R: @claudevdm for label python.

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

Comment thread sdks/python/container/ml/py310/base_image_requirements.txt
@shahar1 shahar1 requested a review from derrickaw July 2, 2026 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants