Skip to content

Drop support for Django 4.2, Django 5.0 and Django 5.1#9899

Open
p-r-a-v-i-n wants to merge 2 commits intoencode:mainfrom
p-r-a-v-i-n:drop-django4.2
Open

Drop support for Django 4.2, Django 5.0 and Django 5.1#9899
p-r-a-v-i-n wants to merge 2 commits intoencode:mainfrom
p-r-a-v-i-n:drop-django4.2

Conversation

@p-r-a-v-i-n
Copy link
Copy Markdown
Contributor

Note: Before submitting a code change, please review our contributing guidelines.

Description

Django 4.2 will reach end of support on April 30, 2026.

I’m opening this PR early so we can have enough time to plan, communicate, and prepare for removing support.

source: https://endoflife.date/django

Copy link
Copy Markdown
Collaborator

@auvipy auvipy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want to wait until the release of django 6.2 LTS

@p-r-a-v-i-n
Copy link
Copy Markdown
Contributor Author

I want to wait until the release of django 6.2 LTS

Okay

@Natgho
Copy link
Copy Markdown
Contributor

Natgho commented Feb 23, 2026

Since it has been developed and stabilized, isn't it a terrible idea to discontinue support immediately? :)
https://endoflife.date/django
As @auvipy said, 4.2 should be supported until 2026.

@browniebroke
Copy link
Copy Markdown
Member

Yes, a bit early for my taste.

I want to wait until the release of django 6.2 LTS

I don't think we need to wait until 6.2 (that's April 2027), but we should definitely wait until 4.2 reaches EOL, which is end of April.

@p-r-a-v-i-n
Copy link
Copy Markdown
Contributor Author

I agree with you all here. I know this is way to early. My intention here was to make ourselves ready, to see any consequences. And once we reach at point where we are confident to drop support. We can do it without any rush.
Probably I already knew this response will come.
So if required I will turn this into draft.

@browniebroke browniebroke added this to the 3.18 milestone Apr 28, 2026
@p-r-a-v-i-n
Copy link
Copy Markdown
Contributor Author

Should we drop django 5.0 and django 5.1 as they both already reached to their EOL?

@browniebroke
Copy link
Copy Markdown
Member

Should we drop django 5.0 and django 5.1 as they both already reached to their EOL?

Waw I didn't realise that they were... I think that makes sense, yes. We'll probably hold off merging this PR for a little bit anyway

@p-r-a-v-i-n p-r-a-v-i-n changed the title Drop support for Django 4.2 Drop support for Django 4.2, Django 5.0 and Django 5.1 Apr 28, 2026
@auvipy
Copy link
Copy Markdown
Collaborator

auvipy commented Apr 28, 2026

let us wait until atleast django 6.0 is released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants