Skip to content

chore(deps): update dependency cryptography to v46#13831

Open
renovate-bot wants to merge 1 commit intoGoogleCloudPlatform:mainfrom
renovate-bot:renovate/cryptography-46.x
Open

chore(deps): update dependency cryptography to v46#13831
renovate-bot wants to merge 1 commit intoGoogleCloudPlatform:mainfrom
renovate-bot:renovate/cryptography-46.x

Conversation

@renovate-bot
Copy link
Contributor

This PR contains the following updates:

Package Change Age Confidence
cryptography (changelog) ==45.0.1==46.0.5 age confidence

Release Notes

pyca/cryptography (cryptography)

v46.0.5

Compare Source

v46.0.4

Compare Source

v46.0.3

Compare Source

v46.0.2

Compare Source

v46.0.1

Compare Source

v46.0.0

Compare Source

v45.0.7

Compare Source

v45.0.6

Compare Source

v45.0.5

Compare Source

v45.0.4

Compare Source

v45.0.3

Compare Source

v45.0.2

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested review from a team as code owners February 15, 2026 11:59
@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels Feb 15, 2026
@product-auto-label product-auto-label bot added samples Issues that are directly related to samples. api: cloudkms Issues related to the Cloud Key Management Service API. api: security-privateca Issues related to the Certificate Authority Service API. labels Feb 15, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @renovate-bot, 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 automates the process of keeping project dependencies up-to-date by upgrading the cryptography library to its latest stable version. This ensures that the project benefits from the most recent security patches, performance improvements, and features provided by the library, maintaining the overall health and security posture of the codebase.

Highlights

  • Dependency Update: The cryptography library has been updated from version 45.0.1 to 46.0.5 across multiple requirements.txt files.
  • Major Version Upgrade: This update includes a major version bump to v46.0.0, which may introduce breaking changes or new features from the cryptography library.
Changelog
  • kms/attestations/requirements.txt
    • Updated the cryptography dependency to 46.0.5.
  • kms/snippets/requirements.txt
    • Updated the cryptography dependency to 46.0.5.
  • privateca/snippets/requirements-test.txt
    • Updated the cryptography dependency to 46.0.5.
Activity
  • This pull request was automatically generated by Renovatebot to update a dependency.
  • Automerge is currently disabled, requiring manual review and merging.
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.

@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Feb 15, 2026
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

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 45.0.1 to 46.0.5. This is a major version update which drops support for Python 3.7.

I've added comments to the requirements.txt files to suggest pinning cryptography conditionally based on the Python version. This will prevent breaking the setup for users on Python 3.7, which appears to be supported based on other conditional dependencies in the project.

@@ -1,4 +1,4 @@
cryptography==45.0.1
cryptography==46.0.5
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The updated cryptography version 46.x drops support for Python 3.7. To maintain compatibility for projects using Python 3.7 (as suggested by the conditional pem dependency), you should specify cryptography versions conditionally based on the Python version. This will ensure that a compatible version of cryptography is used for Python 3.7 environments.

cryptography==45.0.1; python_version < '3.8'
cryptography==46.0.5; python_version >= '3.8'

@@ -1,4 +1,4 @@
google-cloud-kms==3.2.1
cryptography==45.0.1
cryptography==46.0.5
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The updated cryptography version 46.x drops support for Python 3.7. To avoid breaking environments using Python 3.7, you should specify cryptography versions conditionally. This ensures that projects relying on Python 3.7 do not fail during dependency installation.

cryptography==45.0.1; python_version < '3.8'
cryptography==46.0.5; python_version >= '3.8'

pytest==8.2.0
google-auth==2.38.0
cryptography==45.0.1
cryptography==46.0.5
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The updated cryptography version 46.x drops support for Python 3.7. To avoid breaking test environments using Python 3.7, you should specify cryptography versions conditionally. This will ensure the test suite can run on older supported Python versions without installation issues.

cryptography==45.0.1; python_version < '3.8'
cryptography==46.0.5; python_version >= '3.8'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: cloudkms Issues related to the Cloud Key Management Service API. api: security-privateca Issues related to the Certificate Authority Service API. owlbot:run Add this label to trigger the Owlbot post processor. samples Issues that are directly related to samples.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants