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.5 #220

Merged
merged 1 commit into from
Jan 7, 2019
Merged

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented Jan 4, 2019

This PR updates Django from 2.1.4 to 2.1.5.

Changelog

2.1.5

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

*January 4, 2019*

Django 2.1.5 fixes a security issue and several bugs in 2.1.4.

CVE-2019-3498: Content spoofing possibility in the default 404 page
-------------------------------------------------------------------

An attacker could craft a malicious URL that could make spoofed content appear
on the default page generated by the ``django.views.defaults.page_not_found()``
view.

The URL path is no longer displayed in the default 404 template and the
``request_path`` context variable is now quoted to fix the issue for custom
templates that use the path.

Bugfixes
========

* Fixed compatibility with mysqlclient 1.3.14 (:ticket:`30013`).

* Fixed a schema corruption issue on SQLite 3.26+. You might have to drop and
rebuild your SQLite database if you applied a migration while using an older
version of Django with SQLite 3.26 or later (:ticket:`29182`).

* Prevented SQLite schema alterations while foreign key checks are enabled to
avoid the possibility of schema corruption (:ticket:`30023`).

* Fixed a regression in Django 2.1.4 (which enabled keep-alive connections)
where request body data isn't properly consumed for such connections
(:ticket:`30015`).

* Fixed a regression in Django 2.1.4 where
``InlineModelAdmin.has_change_permission()`` is incorrectly called with a
non-``None`` ``obj`` argument during an object add (:ticket:`30050`).


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

@coveralls
Copy link

Coverage Status

Coverage remained the same at 87.846% when pulling 8fa7867 on pyup-update-django-2.1.4-to-2.1.5 into 39bb296 on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 87.846% when pulling 8fa7867 on pyup-update-django-2.1.4-to-2.1.5 into 39bb296 on master.

@nikolas nikolas merged commit aac8b79 into master Jan 7, 2019
@nikolas nikolas deleted the pyup-update-django-2.1.4-to-2.1.5 branch January 7, 2019 14:32
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