Add Django 4.2 and Python 3.11 testing #305
Merged
+35
−43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove Python 3.7, Django 2.2 and 4.0
Also reworked the Github actions CI matrix a bit with the intend to improve maintainability. See commit message for reasoning.
Most controversial change is not including the compatibility check with the current in-development Django. There is not guarantee on how stable it is and I'd rather not see it included by default in our testing matrix. I feel like CI errors that are caused by a bug in Django are something we would want to avoid, not something to ignore when it occurs.
If there is interest, I'd suggest we set up a separate job that periodically runs the tests against the in-development Django.