Repository navigation
[python] update certifi trust bundle to 2026.10.19 - #137
Merged
Merged
Conversation
stevewithey
approved these changes
Oct 21, 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
2 participants
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.
Updates the development/CI lockfile from certifi
2025.1.31to2026.10.19so locked environments use the refreshed CA bundle following the eMudhra intermediate CA compromise. The published SDK dependency constraints are unchanged.Only certifi's version, artifact URLs, and hashes change.
Validation:
uv lock --checkpassed; all 28 SDK tests passed with the updated lockfile; parsed lockfile comparison confirmed every other package and lock metadata is unchanged;git diff --checkpassed. The same certifi release was verified to excludeemSign ECC Root CA - G3and validate HTTPS to PyPI.Part of PLA-164.