Repository navigation
Patch cryptography advisories in publishing dependencies - #31
Merged
Merged
Conversation
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.
Update cryptography 48.0.1 to 50.0.2 in uv.lock, clearing the remaining two high and one medium GitHub advisories. This dependency belongs to the Linux development/publishing chain: twine → keyring → SecretStorage → cryptography; it is not in the exported CLI runtime dependencies.
The initial same-major refresh left these advisories unresolved because their fixes require cryptography 49/50. No application API changes or dependency declarations are needed.
Validation: uv resolves all supported platforms; local pytest suite passes (511 tests); required Python 3.11/3.12/3.13 CI must pass before merge.