Repository navigation
Require patched certifi for emSign CA distrust - #96
Merged
Merged
Conversation
natewalck
self-requested a review
October 23, 2026 13:50
natewalck
approved these changes
Oct 23, 2026
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.
The SDK imports certifi directly to build its HTTPS trust bundle but currently receives an unconstrained transitive version from requests; the lockfile contains certifi 2026.5.20. Declare certifi>=2026.10.19 directly and narrowly refresh its lockfile entry to remove the compromised emSign root. This also applies the minimum to downstream pip installs.
Validation with uv 0.13.4: make install lint test build passed, including all 67 unit tests and both wheel/sdist builds. Runtime code and other dependency versions are unchanged.
Reference: https://discuss.python.org/t/109576