2023-09-04 11:22:22 +00:00
|
|
|
==========================
|
|
|
|
|
Django 4.2.6 release notes
|
|
|
|
|
==========================
|
|
|
|
|
|
2023-09-27 17:18:40 +00:00
|
|
|
*October 4, 2023*
|
2023-09-04 11:22:22 +00:00
|
|
|
|
2023-09-27 17:18:40 +00:00
|
|
|
Django 4.2.6 fixes a security issue with severity "moderate" and several bugs
|
|
|
|
|
in 4.2.5.
|
2023-09-04 11:22:22 +00:00
|
|
|
|
|
|
|
|
Bugfixes
|
|
|
|
|
========
|
|
|
|
|
|
2023-09-11 11:04:32 +00:00
|
|
|
* Fixed a regression in Django 4.2.5 where overriding the deprecated
|
|
|
|
|
``DEFAULT_FILE_STORAGE`` and ``STATICFILES_STORAGE`` settings in tests caused
|
|
|
|
|
the main ``STORAGES`` to mutate (:ticket:`34821`).
|
2023-09-22 04:01:11 +00:00
|
|
|
|
|
|
|
|
* Fixed a regression in Django 4.2 that caused unnecessary casting of string
|
|
|
|
|
based fields (``CharField``, ``EmailField``, ``TextField``, ``CICharField``,
|
|
|
|
|
``CIEmailField``, and ``CITextField``) used with the ``__isnull`` lookup on
|
|
|
|
|
PostgreSQL. As a consequence, the pre-Django 4.2 indexes didn't match and
|
|
|
|
|
were not used by the query planner (:ticket:`34840`).
|
|
|
|
|
|
|
|
|
|
You may need to recreate indexes propagated to the database with Django
|
|
|
|
|
4.2 - 4.2.5 as they contain unnecessary ``::text`` casting that is avoided as
|
|
|
|
|
of this release.
|
