Django 6.1.2 release notesLink to this heading
October 6, 2026
Django 6.1.2 fixes one security issue with severity „low”, three security issues with severity „moderate”, and provides a fix for an insufficient security mitigation in 6.1. It also fixes one data loss issue in 4.0, one infinite loop in 5.2, and several bugs in 6.1.1.
Poprawki błędówLink to this heading
Fixed a data loss issue in Django 4.0 where network rasters were deleted by GeoDjango when closed.
Fixed an infinite loop in Django 5.2 in tuple lookups (e.g.
TupleIn) when anF()expression was used as the left-hand side (#37291).Fixed a bug in Django 6.1 where the
fields.W225system check incorrectly warned thatnullhas no effect onGeneratedField(#37348).Fixed a bug in Django 6.1 where the
UUID4function persisted uppercase values on Oracle. Any data already created using this function on Oracle should be migrated to lowercase so that it can be queried correctly (#37376).Fixed a bug in Django 6.1 where
FETCH_PEERSdid not batch instances loaded byselect_related(), causing unnecessary queries (#37344).Fixed a bug in Django 6.1 where permissions were not renamed for chained
RenameModeloperations, and where permissions with matching codenames on other models in the same app were also renamed (#37361).Fixed a visual regression in Django 6.1 where an extra empty breadcrumb was rendered on the admindocs model index page (#37378).