Skip to content

Conversation

@ulgens
Copy link
Member

@ulgens ulgens commented Dec 4, 2025

Drops support for Django 4.0, 4.1 and 5.0

@oliverandrich
Copy link
Member

For the moment I will keep these minimal versions. Especially, because I have still to upgrade a bunch of projects. And nothing breaks by keeping them.

@ulgens
Copy link
Member Author

ulgens commented Dec 10, 2025

@oliverandrich Thanks for the response.

Those three versions (actually, it became four after the PR, 5.1 is now EOL too) have security issues that won't ever be fixed. If you have any projects in public using those, I'd recommend an immediate update for all of them. On the other hand, any project that uses django-tailwind-cli<=4.4.2 with EOL Django versions can continue to use that combination even when this package removes support for EOL Django versions, because this change won't affect the past versions.

That being said, I'm in no place to act further than strongly recommending it. Please let me know if you change your mind, I can always rebase and test the branch.

@oliverandrich
Copy link
Member

Let me clarify. I am not talking about an indefinite time here. I guess, I will release a version with these changes by the end of the year. We are currently in the finishing touches to convert the last projects to 5.2. I keep you posted.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants