chore(deps): bump cryptography from 50.0.0 to 50.0.1

[dependabot]

Bumps cryptography from 50.0.0 to 50.0.1.

Changelog

Sourced from cryptography's changelog.

50.0.1 - 2026-08-25

* Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 4.0.2.
.. _v50-0-0:

Commits

• ffde75a bump for 50.0.1 + changelog (#15520)
• See full diff in compare view

[claude]

Review

This is a routine Dependabot patch bump (cryptography 50.0.0 → 50.0.1), scoped to a single line in requirements/base.txt. Per upstream's changelog, 50.0.1 only updates the precompiled wheels to be built against a newer OpenSSL — no API/behavior changes.

• Code quality / bugs / performance: N/A — no application code touched.
• Security: This is itself a positive security-maintenance update (keeps cryptography's bundled OpenSSL current). No concerns with taking it.
• Test coverage: No new tests needed for a transitive dependency patch bump; existing suite covers any breakage.

No blockers — looks safe to merge. Recommend letting CI run to confirm the build against the new wheel, then merging (or @dependabot squash and merge if auto-merge is desired).

[JSv4]

@dependabot rebase

[claude]

Review

This is a routine Dependabot patch bump: cryptography 50.0.0 → 50.0.1, a single-line version pin change in requirements/base.txt. Per the release notes, 50.0.1 only updates the precompiled wheels to OpenSSL 4.0.2 (no API changes).

• Code quality / best practices: N/A — no application code touched.
• Bugs: None expected; patch releases from cryptography don't change the public API.
• Performance: No impact.
• Security: This is a net positive — it picks up an OpenSSL update in the vendored wheels, which is exactly the kind of dependency bump that should be merged promptly.
• Test coverage: No new tests needed for a transitive patch bump; CI running the existing test suite against the new pin is sufficient signal.

No concerns — safe to merge once CI passes.