Release `2.7.1` with Django 5.2 support

[realsuayip]

2.8.x release is currently broken:

• Celery Beat silently stops working after period of time, without error #824

and folks depending on django-celery-beat can't upgrade to 5.2 due to strict upper version pinning.

1. Consider releasing 2.7.1, supporting Django 5.2.
2. Consider removing upper version pinning altogether for future, it makes no sense to pin the upper version. Just pin the minimal supported version?

[petrprikryl]

I've create fork for that purpose for anybody also facing same problem: https://github.com/petrprikryl/django-celery-beat/tree/freedom

[auvipy]

why you can not use it? https://github.com/celery/django-celery-beat/blob/main/requirements/runtime.txt

[petrprikryl]

The problem is unresolved 2.8.x scheduling problem: #894
We had this on our project too and couldn't tracked the cause yet :/

[realsuayip]

@auvipy

b2c78b9

this commit does not have 2.7.0 tag so the only way to use django-celery-beat with django 5.2 is to upgrade to >=2.8.0

[auvipy]

please check this comment #956 (comment)