Bump version of encryption sdk to remove cryptography pinning #256
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
kddejong
approved these changes
Apr 17, 2023
mmaeng
approved these changes
Apr 17, 2023
This was referenced Apr 18, 2023
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.
Issue #, if available: #255
Description of changes:
A previous commit pinned the version of
cryptographyto<40.0.0to resolve incompatibility between the version of theaws-encryption-sdkbeing used with this project and the latestcryptographylibrary. However, this package has no direct dependency oncryptographyand theaws-encryption-sdkfixed their compatibility issue with a patch version bump in3.1.1, so we should use that patch version instead of pinning to an older version of a downstream dependency.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.