Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confirm support for Django 4.2 and 5.0, drop support for < 4.2 #166

Merged
merged 4 commits into from
May 9, 2024

Conversation

browniebroke
Copy link
Member

@browniebroke browniebroke commented May 9, 2024

Add Django 4.2 and 5.0 to the test matrix, as they've been released for a while. Python versions supported by each Django version: https://docs.djangoproject.com/en/dev/faq/install/#what-python-version-can-i-use-with-django

It appeared after running tests, but should probably not be tracked
@hramezani
Copy link
Member

Thanks @browniebroke for this PR.

Could you please remove Django 4.1?

@browniebroke
Copy link
Member Author

Should I remove 4.0 as well? 3.2 was LTS but I think its support might just have finished actually...

@browniebroke
Copy link
Member Author

Support for 3.2 ended last month according to https://endoflife.date/django

image

@browniebroke browniebroke changed the title Confirm support for Django 4.2 and 5.0 Confirm support for Django 4.2 and 5.0, drop support for 4.0 and 4.1 May 9, 2024
@hramezani
Copy link
Member

Should I remove 4.0 as well? 3.2 was LTS but I think its support might just have finished actually...

Yes, please remove both

@hramezani hramezani merged commit 625969b into jazzband:master May 9, 2024
6 checks passed
@browniebroke browniebroke deleted the django-5.0-support branch May 9, 2024 18:25
@browniebroke browniebroke changed the title Confirm support for Django 4.2 and 5.0, drop support for 4.0 and 4.1 Confirm support for Django 4.2 and 5.0, drop support for < 4.2 May 9, 2024
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.

None yet

2 participants