Skip to content

[Snyk] Security upgrade cryptography from 45.0.7 to 46.0.6 #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
madisonmay wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade cryptography from 45.0.7 to 46.0.6 #65

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions requirements/test.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,3 +7,4 @@ moto>=2.2.6
pre-commit
-r extras/yaml.txt
-r extras/msgpack.txt
cryptography>=46.0.6 # not directly required, pinned by Snyk to avoid a vulnerability
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot Mar 29, 2026

Choose a reason for hiding this comment

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

P1 Badge Avoid forcing cryptography>=46 in Python 3.7 test envs

This new unconditional requirement applies to every tox environment that installs requirements/test.txt, including the Python 3.7 jobs still configured in tox.ini and .github/workflows/python-package.yml. cryptography 46.x no longer provides Python 3.7-compatible distributions, so this bound makes dependency resolution fail before tests run in those environments. The version floor should be guarded with a Python-version marker (or equivalent split constraint) so 3.7 jobs can still install dependencies.

Useful? React with 👍 / 👎.

Loading