Repository navigation
Python SDK 0.5.1: require patched CA trust - #5
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
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.
Python SDK 0.5.1 requires certifi>=2026.10.19 so existing environments cannot retain the CA trust paths affected by the October 2026 eMudhra compromise. CI uses uv 0.13.4. Explicit caller-provided custom CA bundles remain caller-managed. No API behavior changes.
Validation: 121 mocked API/unit tests, lint, wheel/sdist builds passed; built wheel metadata verified the certifi floor. SDK additionally passed strict type and formatting checks. PyPI publication is a separate release step.