Repository navigation
Python 3.15 - #43
Merged
Merged
Python 3.15#43
Conversation
Moves the image and CI from Python 3.13 to 3.15, which clears CVE-2025-15367 from the image. The lock files are recompiled for 3.15 with the same pinned versions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
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
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.
Why
The image runs Python 3.13.18, which grype flags for CVE-2025-15367 (Medium). That finding doesn't apply to Python 3.15.
What
Moves the Docker image and the API CI job from Python 3.13 to 3.15, and recompiles both lock files for 3.15. Every pinned version and hash stays the same.
Verification
pip-style install with--require-hashesruff check cryptex teststests/reference.pydocs/vectors.jsonunchangedpytestpythonremain, fixed only in 3.16🤖 Generated with Claude Code