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 to 2.1.3 #215

Merged
merged 1 commit into from
Nov 2, 2018
Merged

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented Nov 1, 2018

This PR updates Django from 2.1.2 to 2.1.3.

Changelog

2.1.3

==========================

*November 1, 2018*

Django 2.1.3 fixes several bugs in 2.1.2.

Bugfixes
========

* Fixed a regression in Django 2.0 where combining ``Q`` objects with ``__in``
lookups and lists crashed (:ticket:`29838`).

* Fixed a regression in Django 1.11 where ``django-admin shell`` may hang
on startup (:ticket:`29774`).

* Fixed a regression in Django 2.0 where test databases aren't reused with
``manage.py test --keepdb`` on MySQL (:ticket:`29827`).

* Fixed a regression where cached foreign keys that use ``to_field`` were
incorrectly cleared in ``Model.save()`` (:ticket:`29896`).

* Fixed a regression in Django 2.0 where ``FileSystemStorage`` crashes with
``FileExistsError`` if concurrent saves try to create the same directory
(:ticket:`29890`).


==========================
Links

@coveralls
Copy link

Coverage Status

Coverage remained the same at 87.846% when pulling 9614766 on pyup-update-django-2.1.2-to-2.1.3 into cd48a61 on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 87.846% when pulling 9614766 on pyup-update-django-2.1.2-to-2.1.3 into cd48a61 on master.

@sdreher sdreher merged commit c74c5c0 into master Nov 2, 2018
@ndittren ndittren deleted the pyup-update-django-2.1.2-to-2.1.3 branch October 7, 2022 17:23
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.

3 participants