Drop Django 4.2, add Django 6.1

[mgrdcm]

4.2 past extended support, 6.1 just released

[SmileyChris]

Thanks for this — I've landed the Django 6.1 half in c433dc1, with you as co-author.

I split it rather than merging as-is, for two reasons:

Django 4.2 stays for now. You're right that it's past end of life (7 April 2026), but dropping it is a breaking change, so it belongs in 10.0 rather than a minor. Tracking that in #497, with your checklist essentially intact.

The DRF pins needed to move too. That's what the red CI here was: DRF 3.17 imports cc_delim_re from django.utils.cache, which Django 6.1 removed, so all three latest envs failed to collect test_drf.py. The latest env is now Django 6.1 + DRF 3.18. Worth noting for 10.0 — DRF 3.18 requires django>=5.2, so the legacy env can't follow it up while 4.2 is still in the matrix.

Closing in favour of #497. Appreciate you keeping an eye on the support window — this is the second time you've caught it.

[SmileyChris]

Django 6.1 support is out in 9.1.0. Thanks again!

[mgrdcm]

Django 4.2 stays for now. You're right that it's past end of life (7 April 2026), but dropping it is a breaking change, so it belongs in 10.0 rather than a minor. Tracking that in #497, with your checklist essentially intact.

Good call on switching that to a breaking change, much better that way!

Closing in favour of #497. Appreciate you keeping an eye on the support window — this is the second time you've caught it.

Glad I can help!