Django 1.6 end of life (EOL) date and support status
End of life End of life since 2015-04-01 (4208 days ago)
Upgrade: Django 1.6 no longer receives fixes. Supported cycles: 6.1, 6.0, 5.2.
| Product | Django |
|---|---|
| Version cycle | 1.6 |
| Status | End of life |
| Released | 2013-11-06 |
| Active support until | 2014-09-02 |
| End of life | 2015-04-01 |
| Latest version | 1.6.11 (2015-03-18) |
| Last verified | 2026-10-08 |
All Django versions → · Source: endoflife.date
Frequently asked questions
Is Django 1.6 end of life?
Yes. End of life since 2015-04-01 (4208 days ago). It no longer receives security or bug fixes.
When does Django 1.6 reach end of life?
Django 1.6 reached end of life on 2015-04-01.
When was Django 1.6 released?
Django 1.6 was first released on 2013-11-06.
What is the latest Django 1.6 version?
The latest 1.6 release is 1.6.11, published on 2015-03-18.
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/1.6