fix(deps): allow cryptography 50 so pip-audit passes - #278
Merged
Conversation
PYSEC-2026-3552 affects cryptography 49.0.0 and is fixed in 50.0.0, which the existing `<50` cap excluded. Every PR in the repo fails the Security scan job until the cap moves; main last ran CI before the advisory landed, so this is not a regression from any one change. Cap only. The floor stays at 42 rather than jumping to 50, because raising it forces the bump on every consumer for an advisory whose impact on this package has not been assessed. If it turns out to matter here, the floor is a separate, deliberate change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
pip-auditfails on every open PR:The pin was
cryptography>=42,<50, which excludes the fixed release.mainlast ran CI on 2026-08-03, before the advisory landed, so this is not a regression from any one PR — it blocks all of them (#277, #274, #270).Cap widened to
<51. The floor stays at 42 deliberately: raising it forces the bump on every consumer for an advisory whose impact on this package has not been assessed. If it turns out to matter here, the floor is a separate and deliberate change.🤖 Generated with Claude Code