Django 6.1 released

The Django team has released Django 6.1, announced on the Django Weblog. The release notes mix new features with usability improvements rather than a single headline change.

Model field fetch modes let developers configure on-demand fetching for model fields, so load behavior can be set per field instead of only through default query patterns. Database-level delete options for ForeignKey.on_delete move cascade and related delete policy into the database where the relation is defined. Dictionary-based email settings replace more scattered email configuration with a structured dictionary form.

For engineers shipping Django apps, fetch modes matter when large models or optional relations make N-plus-one queries and over-fetching hard to control. Database-level delete options matter when integrity and cascade behavior must stay correct under concurrent writes and not only inside the application layer. Dictionary-based email settings matter when environments, queues, and multi-backend mail setups need configuration that is easier to version and review.

These changes sit in the same lane as other mature web frameworks that push more data-access and config control into explicit, inspectable surfaces instead of implicit defaults. Django remains the default stack for many Python product and internal tools teams; 6.1’s highlights are incremental framework depth, not a new product category.

If you maintain a Django codebase, read the 6.1 release notes for fetch modes, ForeignKey.on_delete database options, and email settings before upgrading. Plan how on-demand field fetch and database-level deletes map onto your current models and migrations, and migrate email config to the dictionary form where it reduces environment drift.