Pin boto3<1.36.0 because 1.36 introduces breaking changes #270
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
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.
boto3 1.36.0 introduces incompatible changes with non-AWS S3 providers related with integrity checksums: boto/boto3#4392
In our case, it resulted in MissingContentMD5 error thrown by MinIO on DeleteObjects call #269 because boto3 1.36.0 completely removes
Content-MD5evaluation and that's a required header by our MinIO version. Evaluation removal was done here: boto/botocore@590103b#diff-6430b10ddffa7de73a08acc48a810a748dc2b01197c28fc974699d3d1fe9e4ffL1362MinIO adds support for new integrity checksums in fresh release:
but as we don't explicitly require a specific S3 provider and boto3 has still compatibility issues with non-AWS ones, it's much more safe to pin to the previous version for a while and wait until issues are resolved.
closes #269