Repository navigation
Security: update certifi after eMudhra CA compromise - #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.
Updates only certifi's locked package record to 2026.10.19, using the PyPI release artifact SHA-256 hashes. All other package records and lock metadata are checked unchanged; no model, numeric, framework, or architecture source is modified.
Validation: lockfiles parse, only certifi changes, release wheel hash matches PyPI, and the patched bundle rejects all 14 published incident TLS chains. Installed environments, cached images and running jobs require their own update/restart and real-client verification. This source change alone does not establish deployment remediation.
Incident: https://emudhra.we-have-a-problem.com/