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 #100

Merged
merged 1 commit into from
Nov 1, 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

Pull Request Test Coverage Report for Build 158

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 45.846%

Totals Coverage Status
Change from base Build 138: 0.0%
Covered Lines: 298
Relevant Lines: 650

💛 - Coveralls

@NicolasLM NicolasLM merged commit 9b5bb26 into master Nov 1, 2018
@NicolasLM NicolasLM deleted the pyup-update-django-2.1.2-to-2.1.3 branch November 27, 2018 09:30
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.

None yet

3 participants