126 wires and counting

$ follow Django

Keep up with Django in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-09-20
stories 7

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Django drops PostgreSQL 15 and PostGIS 3.2, patches an admin date_hierarchy 500

By RepoJournal · Filed · About Django · Composed from the cited sources · methodology

Two changes landed in django/django today that will show up in your own deployments: a supported-database floor that rises when you upgrade, and a one-line fix for an unhandled 500 in the admin.

Fixed #37114 -- Dropped support for PostgreSQL 15 and PostGIS 3.2. django/django

by felixxm

Mariusz Felisiak's change removes PostgreSQL 15 and PostGIS 3.2 from the supported matrix. Once you're on the release carrying this, the older database and GIS backend are no longer covered, so check your own CI before upgrading.

Fixed #37357 -- Handled out-of-range year in admin date_hierarchy. django/django

by Philip Sørensen

ChangeList.get_filters() caught ValueError only around the datetime() construction, leaving the to_date computation outside the try, so a query like ?date__year=9999 (year + 1 == 10000) or a value too large for a C long escaped as an unhandled exception and an HTTP 500 instead of the intended IncorrectLookupParameters redirect. Both exceptions are now caught and to_date moves inside the try.

Fixed #37357 -- Handled out-of-range year in admin date_hierarchy. django/django

by philipsorensen

Philip Sørensen reports the out-of-range year query parameter escaping as an unhandled exception rather than the ?e=1 redirect the changelist view is supposed to produce. The bug only fires when an admin user can put an arbitrary year into a date_hierarchy URL, which makes it a robustness fix rather than a security one.

Refs #36947 -- Added supports_comments skip to test_alter_generated_field_base_field_comment. django/django

by Tim Graham

Tim Graham adds a supports_comments skip to test_alter_generated_field_base_field_comment, keeping that generated-field test from running on backends that don't support comments.

Results for ubuntu-latest added [skip ci] django/django-asv

by Github Bot

Elsewhere, the benchmark bot added ubuntu-latest results to django/django-asv, quiet infrastructure work with no reader-facing change.

Quick answers

What shipped in Django on September 20, 2026?
Two changes landed in django/django today that will show up in your own deployments: a supported-database floor that rises when you upgrade, and a one-line fix for an unhandled 500 in the admin. In total, 4 commits and 3 pull requests landed.
Who contributed to Django on September 20, 2026?
3 developers shipped this update, including Mariusz Felisiak, philipsorensen, and Tim Graham.
What were the notable Django updates?
Fixed #37114 -- Dropped support for PostgreSQL 15 and PostGIS 3.2, Fixed #37357 -- Handled out-of-range year in admin date_hierarchy, and Fixed #37357 -- Handled out-of-range year in admin date_hierarchy.