Bump Cryptography, pin the py2 version separately #1282
Merged
Conversation
This file contains 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
On Python3 bump cryptography from 3.3.1 to 3.4.5. On python2 bump from 3.3.1 to 3.3.2 (3.3-branch is the last branch with python2 support). Signed-off-by: Jussi Kukkonen <jkukkonen@vmware.com>
jku
force-pushed
the
pin-cryptography
branch
from
e3960d4
to
b5304e4
Compare
joshuagl
approved these changes
Feb 16, 2021
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.
On Python3 bump cryptography from 3.3.1 to 3.4.5.
On python2 bump from 3.3.1 to 3.3.2 (3.3-branch is the last branch
with python2 support).
Signed-off-by: Jussi Kukkonen jkukkonen@vmware.com
I think this is enough in TUF? -- once securesystemslib releases we can change TUF setup.py to require the new securesystemslib and that will bring in the correct cryptography for the binary packages?