Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update django-storages to 1.6.5 #87

Closed
wants to merge 1 commit into from

Conversation

pyup-bot
Copy link
Collaborator

There's a new version of django-storages available.
You are currently using 1.6.3. I have updated it to 1.6.5

These links might come in handy: PyPI | Changelog | Repo

Changelog

1.6.5


  • Fix Django 1.11 regression with gzipped content being saved twice
    resulting in empty files (367, 371, 373_)
  • Fix the mtime when gzipping content on S3Boto3Storage (374_)

.. _367: jschneier/django-storages#367
.. _371: jschneier/django-storages#371
.. _373: jschneier/django-storages#373
.. _374: jschneier/django-storages#374

1.6.4


  • Files uploaded with GoogleCloudStorage will now set their appropriate mimetype (320_)
  • Fix DropBoxStorage.url to work. (357_)
  • Fix S3Boto3Storage when AWS_PRELOAD_METADATA = True (366_)
  • Fix S3Boto3Storage uploading file-like objects without names (195, 368)
  • S3Boto3Storage is now threadsafe - a separate session is created on a
    per-thread basis (268, 358)

.. _320: jschneier/django-storages#320
.. _357: jschneier/django-storages#357
.. _366: jschneier/django-storages#366
.. _195: jschneier/django-storages#195
.. _368: jschneier/django-storages#368
.. _268: jschneier/django-storages#268
.. _358: jschneier/django-storages#358

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

@brudil brudil closed this Sep 1, 2017
@brudil brudil deleted the pyup-update-django-storages-1.6.3-to-1.6.5 branch September 1, 2017 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants