Test PR: pin azure-storage-blob#7242
Closed
daviddavis wants to merge 1 commit into
Closed
Conversation
mdellweg
reviewed
Jan 23, 2026
| s3 = ["django-storages[boto3]==1.14.6"] | ||
| google = ["django-storages[google]==1.14.6"] | ||
| azure = ["django-storages[azure]==1.14.6"] | ||
| azure = ["django-storages[azure]==1.14.6", "azure-storage-blob<12.28.0"] |
Member
There was a problem hiding this comment.
That's something we have covered by the ci_constraints. I don't expect this to change a thing...
Contributor
Author
There was a problem hiding this comment.
I see. It seems like there is a very old version of azure-storage-blob that might work but even 12.25.1 seems to have compatibility issues. I think I'll go with the other PR to skip the api version check in azurite.
daviddavis
force-pushed
the
pin-azure-storage-blob
branch
from
85a1c3c to
60186f5
Compare
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
2 participants
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.
A temporary fix until Azure/Azurite#2623 is resolved.