New release to PyPI is required for Django v5.1

[cclauss]

Summary:

• Remove Strict Upper Version Limit for Django #755
• relaxed django upper version limit to 5.1 #756
• Start testing on Django v5.1 #761
• https://pypi.org/project/Django is currently v5.1.

Installing django-celery-beat on Django v5.1 will downgrade:
django-celery-beat: 2.6.0 --> 2.1.0
django-timezone-field: 7.0.0 --> 4.2.3

Exact steps to reproduce the issue:

1. pip install Django django-celery-beat

Detailed information

This problem has been fixed on the main branch of this repo but that code has not been published to PyPI.

[auvipy]

I will try to do this this week end saturday / sunday. feel free to ping me on friday night so that I can see it im sonntag

[cclauss]

Ping. ;-) I am attending some live music this evening but after that I will create a #739-like pr if you have not already done so.

• Update Changelog for v2.6.0 #739

[cclauss]

OK.

• The DRAFT v2.7.0 release is now at https://github.com/celery/django-celery-beat/releases
• When ready please copy that text to the top of Changelog.
  • Or Update changelog for v2.7.0 #783
• Ensure that bumpversion updates the version in files:
  • .bumpversion.cfg, README.rst, django_celery_beat/__init__.py, and docs/includes/introduction.txt
• Build and publish via ci: add a github workflow to build and publish #749

[cclauss]

@auvipy please let me know if you have any questions.

[mrzorn]

Any updates on when the 2.7.0 release is planned?

[auvipy]

@auvipy please let me know if you have any questions.

you have to take responsibility of this release! and update the release documentation based on current scenario. Due to some gap, I am hesitant. and some personal / professional emergency arise lately.

[cclauss]

OK... Will do.

[Nusnus]

OK... Will do.

Let me know if you need a hand ✋@cclauss

[vasilistotskas]

release on pypi ?

[Nusnus]

release on pypi ?

@cclauss you should be able to release on pypi now

[cclauss]

https://pypi.org/p/django-celery-beat 👍 🎉 🚀 📦