Django 3.2 end of life (EOL) date and support status
End of life End of life since 2024-04-01 (920 days ago)
Upgrade: Django 3.2 no longer receives fixes. Supported cycles: 6.1, 6.0, 5.2.
| Product | Django |
|---|---|
| Version cycle | 3.2 |
| Status | End of life |
| Released | 2021-04-06 |
| LTS | yes |
| Active support until | 2021-12-07 |
| End of life | 2024-04-01 |
| Latest version | 3.2.25 (2024-03-04) |
| Last verified | 2026-10-08 |
All Django versions → · Source: endoflife.date
Frequently asked questions
Is Django 3.2 end of life?
Yes. End of life since 2024-04-01 (920 days ago). It no longer receives security or bug fixes.
When does Django 3.2 reach end of life?
Django 3.2 reached end of life on 2024-04-01.
When was Django 3.2 released?
Django 3.2 was first released on 2021-04-06.
What is the latest Django 3.2 version?
The latest 3.2 release is 3.2.25, published on 2024-03-04.
Is Django 3.2 an LTS release?
Yes.
Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
For agents
GET https://vigia.coredls.cloud/v1/eol/django/3.2