Skip to content

build(deps): bump cryptography from 46.0.7 to 48.0.1 #30

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

Merged
haasonsaas merged 1 commit into from
Jun 20, 2026
Merged

build(deps): bump cryptography from 46.0.7 to 48.0.1 #30

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
2 changes: 1 addition & 1 deletion requirements_lock.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ coverage==7.10.7
# via pytest-cov
croniter==6.0.0
# via rq
cryptography==46.0.7
cryptography==48.0.1

@cursor cursor Bot Jun 17, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Lock files diverge on cryptography

High Severity

This change sets cryptography==48.0.1 in requirements_lock.txt while uv.lock still pins 46.0.7. Makefile regenerates requirements_lock.txt from uv.lock, and the Dockerfile installs with uv sync --frozen, so deployed images keep the old release while Bazel uses the bumped export.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit a68a25b. Configure here.

# via pyjwt
distro==1.9.0
# via openai
Expand Down
Loading