Repository navigation
馃悰 fix(seed): upgrade embedded pip to 26.2.2 - #3459
Closed
shaanmajid wants to merge 2 commits into
Closed
shaanmajid wants to merge 2 commits into
shaanmajid wants to merge 2 commits into
Conversation
pip 26.2.2 vendors certifi 2026.10.19, which drops emSign ECC Root CA - G3 after the eMudhra intermediate CA key compromise.
Author
|
The workflows to get CI green here need to be explicitly ran by a maintainer. Not sure if I should keep in draft until then or not haha |
Contributor
|
Hey, thanks for opening this pull request. We have automation for this, which I triggered, and this is superseded by that, as that provides a more complete solution. Thank you. #3452 |
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.
Upgrade the embedded pip wheel from 26.2.1 to 26.2.2 (Python 3.10+).
pip 26.2.2 vendors certifi 2026.10.19, which removes emSign ECC Root CA - G3 after eight eMudhra intermediate CA keys were compromised (disclosure). pip loads its vendored certifi on top of the system store, so a venv seeded with 26.2.1 trusts certificates from those keys when installing from PyPI.
This bump is in advance of the scheduled workflow and 7-day cooldown given the severity of the issue. I would recommend merging and releasing ASAP to mitigate any impact for downstream virtualenv consumers.
See:
To verify the embedded wheel is identical to PyPI's:
Python 3.9 stays on pip 26.0.1, since 26.2.x needs 3.10.
tox -e fix)docs/changelogfolderpyvenv.cfg, wheel downloads, app-data or release workflows: explained in the PR text which outside input the change handles, such as a path, a prompt or a downloaded file, and how it stops that input from running as code. See the security scope.tox run -e 3.9,3.15)