Django Releases
Track every Django release from latest stable to end-of-life. Version timelines, LTS support, Python compatibility, async evolution, and upgrade guidance for Python web teams.
—
Total Versions
—
Supported
—
Latest
Version Timeline
All tracked releases with lifecycle status and EOL dates.
Loading version data…
Lifecycle Timeline
Visual overview of active support and maintenance windows.
Upgrade Paths
Migration guidance between major versions — breaking changes, effort estimates, and tips.
Breaking Changes
- Python 3.10+ required (drops 3.8, 3.9)
- Default form rendering changed to div-based (was table/p)
- Faceted filters in admin by default
- Database-computed default values
- GeneratedField for database-level computed columns
Migration Notes
The Python version bump is the biggest blocker. If you are on Python 3.8/3.9, upgrade Python first. Form rendering changes may affect custom CSS targeting <table> or <p> elements in forms. Run django-upgrade --target-version 5.0 to automate code changes.
Breaking Changes
- LoginRequiredMiddleware added (opt-in)
- Querystring token-based password reset (more secure)
- Admin improvements (column resizing, dark mode fixes)
- db_default for model fields
Migration Notes
Straightforward upgrade. LoginRequiredMiddleware is opt-in so it does not break existing auth flows. Run django-upgrade and test.
Breaking Changes
- Composite primary keys (CompositeKey) — opt-in
- Automatic model imports in shell
- Improved constraint validation
- Simplified auth backend configuration
Migration Notes
This is the next LTS target. All changes are additive. Composite primary keys are opt-in and do not affect existing models. Ideal landing version for teams wanting long-term stability (supported until April 2028).
Breaking Changes
- Python 3.10+ required
- All changes from 5.0 and 5.1 above
- Form rendering changed to div-based
- Multiple deprecation removals accumulated across 3 versions
Migration Notes
LTS-to-LTS jump. Recommended path: upgrade Python first, then Django 4.2 → 5.0 → 5.2 (skipping 5.1 is fine). Run django-upgrade at each step. Fix deprecation warnings before jumping. Budget half a day for a medium-sized app.
Version Risk Assessment
Evaluate risk factors before choosing a version for production.
| Version | EOL Risk | CVE Risk | Ecosystem | Cloud Support | Overall | Recommended Action |
|---|---|---|---|---|---|---|
| Django 3.2 LTS & below | Critical | High | Unsupported | Dropping | Critical | Past EOL — no security patches, upgrade immediately |
| Django 4.0 / 4.1 | Critical | Medium | Degrading | Legacy | Critical | Past EOL — upgrade to 4.2 LTS or 5.2 |
| Django 4.2 LTS | Medium | Low | Active | Full | Medium | Supported until Apr 2026 — plan upgrade to 5.2 LTS |
| Django 5.0 | High | Low | Active | Full | High | EOL Apr 2025 — upgrade to 5.1 or 5.2 |
| Django 5.1 | Low | Low | Active | Full | Low | Supported until Dec 2025 — current stable |
| Django 5.2 LTS | None | Low | Growing | Full | Low | Next LTS — recommended target for production |
Risk combines EOL proximity, Python version requirements, security patch availability, and third-party library support. Assessed as of March 2026.
Feature Release Comparison
Side-by-side feature differences across major versions.
| Feature | 4.2 LTS | 5.0 | 5.1 | 5.2 LTS |
|---|---|---|---|---|
| Python minimum | 3.8 | 3.10 | 3.10 | 3.10 |
| Python maximum | 3.12 | 3.12 | 3.13 | 3.13 |
| Async views | Stable | Stable | Stable | Stable |
| Async ORM | Partial | Expanded | Expanded | Full |
| Composite primary keys | No | No | No | Stable |
| GeneratedField | No | Stable | Stable | Stable |
| db_default | No | No | Stable | Stable |
| LoginRequiredMiddleware | No | No | Stable | Stable |
| Form rendering | table/p | div-based | div-based | div-based |
| Admin dark mode | Partial | Partial | Improved | Improved |
| LTS support until | Apr 2026 | N/A | N/A | Apr 2028 |
| Security support ends | Apr 2026 | Apr 2025 | Dec 2025 | Apr 2028 |
Embed Badges
Add live Django status badges to your README, docs, or dashboard.
Health Status
Overall support health
EOL Countdown
Next end-of-life date
Latest Version
Current stable release
CVE Status
Known vulnerabilities
Frequently Asked Questions
Common questions about Django releases and lifecycle.