chore(deps): upgrade to Django 6.1 using django-celery-beat-next #57

New issue

Closed

opened 2026-10-31 20:55:47 +00:00 by Gilles · 0 comments

Gilles commented

2026-10-31 20:55:47 +00:00

Owner

django-celery-beat 2.9.0 (latest) still pins Django<6.1, which blocks the Django 6.1 upgrade (Renovate PR #4 fails CI).

django-celery-beat-next is a drop-in fork (same django_celery_beat module, Django<6.2). Use it temporarily, and switch back to upstream django-celery-beat once it officially supports Django 6.1.

django-celery-beat 2.9.0 (latest) still pins `Django<6.1`, which blocks the Django 6.1 upgrade (Renovate PR #4 fails CI). [django-celery-beat-next](https://pypi.org/project/django-celery-beat-next/) is a drop-in fork (same `django_celery_beat` module, `Django<6.2`). Use it temporarily, and switch back to upstream `django-celery-beat` once it officially supports Django 6.1.

Gilles added the

dependencies

label

2026-10-31 20:55:47 +00:00

Gilles referenced this issue from a commit

2026-10-31 20:56:42 +00:00

chore(deps): upgrade to Django 6.1 using django-celery-beat-next

Gilles referenced this issue from a pull request that will close it,

2026-10-31 20:56:43 +00:00

chore(deps): upgrade to Django 6.1 using django-celery-beat-next #58

Gilles closed this issue

2026-10-31 21:00:23 +00:00