Repository navigation
Conversation
Older pip releases still trust the withdrawn emSign root CA certificate, so require a newer pip and updated certificate packages. - Upgrade pip to >=26.2.2 in the documentation workflow before installing Sphinx. - Document the pip requirement and add an explicit pip upgrade step in installation.md. - Unpin ca-certificates and set certifi>=2026.10.19 and pip>=26.2.2 in se3_flow_matching/fm.yml.
This branch has not been deployed
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
1 participant
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.
Older pip releases still trust the withdrawn emSign root CA certificate, so require a newer pip and updated certificate packages.
This change is in response to the security issues outlined in: https://discuss.python.org/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576/47