Upgrade planner
Where can I upgrade from Django 2.0?
Supported upgrade options use CompatHub lifecycle status. Compatibility and vulnerability context appear only when evidence already exists — missing data is never treated as a negative conclusion.
You are on Django 2.0
End of lifeEND OF LIFE
- EOL
- 1 April 2019
- Latest release
- —
Currently recorded vulnerabilities: 30. Currently recorded vulnerabilities (coverage may be incomplete).
Supported upgrade options
Newer version lines that are not end-of-life, ranked by remaining support then version. CompatHub does not mark a single option as recommended.
- Django 5.2View Django 5.2 →SupportedEXTENDED SUPPORT
- EOL
- 1 April 2028
- Latest release
- 5.2.17
- Upgrade distance
- 3 major versions newer
- Support difference
- ~108 months more support
Currently recorded vulnerabilities: 41. Currently recorded vulnerabilities (coverage may be incomplete).
- Django 6.1View Django 6.1 →SupportedSTANDARD SUPPORT
- EOL
- 1 December 2027
- Latest release
- 6.1
- Upgrade distance
- 4 major versions newer
- Support difference
- ~104 months more support
No vulnerabilities currently recorded by CompatHub.
- Django 6.0View Django 6.0 →SupportedEXTENDED SUPPORT
- EOL
- 1 April 2027
- Latest release
- 6.0.8
- Upgrade distance
- 4 major versions newer
- Support difference
- ~96 months more support
Currently recorded vulnerabilities: 49. Currently recorded vulnerabilities (coverage may be incomplete).