Django 6.1 Ships as Django 6.0 Exits Mainstream Support
The framework's twice-yearly release lands with new field-level and delete controls, and starts the clock on retiring the previous release.
The Django project released Django 6.1 on August 5, 2026, continuing its regular release cadence. The new version adds model field fetch modes, letting developers configure on-demand fetching behavior for specific fields rather than relying on Django's default query behavior for every field on a model.
It also adds database-level delete options for ForeignKey.on_delete, moving some referential-integrity enforcement down to the database itself rather than leaving it entirely to Django's application-level handling. The release rounds out with dictionary-based email settings, giving developers a more structured way to configure Django's modernized email API without stringing together as many individual settings.
The release also marks a transition point for the previous version: Django 6.0 has now exited mainstream support, with 6.0.8 shipped August 4, 2026 as its final scheduled minor release. Django's support policy still guarantees security and data-loss fixes for 6.0 through April 2027, so existing 6.0 deployments aren't left exposed immediately, but new feature work and routine bug fixes will only land in 6.1 and later going forward.
Django ships on a predictable schedule -- a new feature release roughly every eight months, alternating between versions that get extended long-term support and ones that don't -- specifically so teams can plan upgrades around a known calendar rather than reacting to unannounced releases. 6.1 follows that same rhythm, arriving on schedule after 6.0 shipped in December 2025.
Teams currently on 6.0 aren't forced to move immediately given the security-fix runway through April 2027, but the usual upgrade guidance applies: check the release notes for backwards-incompatible changes before bumping the version, particularly around any code relying on the previous default fetch behavior that the new field fetch modes are meant to make explicit and configurable instead.