6.1 released 5 August 2026, latest 6.1.
Django 6.1 is currently supported. Active support is scheduled to end on 30 April 2027. It reaches end of life on 31 December 2027.
What changed
No upstream Django 6.1 release notes or stable API documentation are available to substantiate a feature-by-feature account of changes from the preceding line. Treat any claimed list of new framework features, removals, or compatibility breaks for this cycle as unverified until it can be checked against Django’s published release notes and deprecation timeline.
What staying costs
The cycle is stated to be actively supported, so remaining on it does not by itself create an immediate loss of upstream maintenance coverage. The trade-off is that later supported Django lines can accumulate security fixes, bug fixes, compatibility work, and completed deprecation removals. Delaying a move can also increase the eventual upgrade delta, particularly where an application relies on deprecated Django APIs, third-party packages, or database and Python integrations with their own support policies.
What to do
Keep the application on the latest patch release in the 6.1 line and monitor Django’s security advisories, release notes, and deprecation documentation. In a representative test environment, run the full application and dependency test suite with warnings treated as actionable, inventory deprecated APIs and version-constrained packages, and verify supported Python, database, cache, and package versions. Establish a repeatable upgrade branch for the next supported Django line, then use its published release notes to scope and test the concrete migration work before production adoption.
We can tell you what moving off Django 6.1 involves.
What it takes to move off Django 6.1 depends on what you built on it — the version you are on, how much depends on it, and how much of the work is mechanical. Leave your email with this version and we can tell you what that looks like for you.
Not sure yet? Get my plan