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 1.11.9 #27

Merged
merged 1 commit into from
Jan 3, 2018
Merged

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented Jan 2, 2018

There's a new version of Django available.
You are currently using 1.11.8. I have updated it to 1.11.9

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

Changelog

1.11.9

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

January 1, 2018

Django 1.11.9 fixes several bugs in 1.11.8.

Bugfixes

  • Fixed a regression in Django 1.11 that added newlines between MultiWidget's
    subwidgets (:ticket:28890).
  • Fixed incorrect class-based model index name generation for models with
    quoted db_table (:ticket:28876).
  • Fixed incorrect foreign key constraint name for models with quoted
    db_table (:ticket:28876).
  • Fixed a regression in caching of a GenericForeignKey when the referenced
    model instance uses more than one level of multi-table inheritance
    (:ticket:28856).

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

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

Happy merging! 🤖

@coveralls
Copy link

coveralls commented Jan 2, 2018

Coverage Status

Coverage remained the same at 92.593% when pulling f4dec57 on pyup-update-django-1.11.8-to-1.11.9 into 11061eb on master.

@nikolas nikolas merged commit a0786a0 into master Jan 3, 2018
@ndittren ndittren deleted the pyup-update-django-1.11.8-to-1.11.9 branch January 24, 2024 17:19
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