Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare for release v2.6.0 to support Py3.12 and Dj5.0 #712

Merged
merged 3 commits into from
Jan 11, 2024
Merged

Prepare for release v2.6.0 to support Py3.12 and Dj5.0 #712

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
35a3f5d
Prepare for release v2.6.0 to support Py3.12 and Dj5.0
cclauss Jan 10, 2024
76e33a6
Update Changelog
cclauss Jan 11, 2024
34111ca
Changelog: Add a blank line to placate the linter.
cclauss Jan 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 20 additions & 1 deletion Changelog
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,26 @@

Next
====
- Formally support Python 3.12.


2.6.0
=====
release-date: !!! FIX_ME !!!
cclauss marked this conversation as resolved.
Show resolved Hide resolved
:release-by: !!! FIX_ME !!!
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @cclauss,

Please help me understand, are these dynamically generated?

Copy link
Contributor Author

@cclauss cclauss Jan 11, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not a project maintainer so I do not know if there are tools for the dynamic generation of release notes.

I merely looked at previous entries in this file and at https://github.com/celery/django-celery-beat/releases and then manually built this similar content. If maintainers have a better approach then this might go in the trash bin.

Thanks for your review (the checkmark in the upper right of this page). I wish more visitors would take that approach because it is usually more convincing to project maintainers than scads of 👍 and 🚀 emojis.

cclauss marked this conversation as resolved.
Show resolved Hide resolved
- Formally support Python 3.12. (#690)
- Avoid crash when can not get human readable description (#648)
- Update codeql-analysis.yml (#653)
- Celery Beat scheduled tasks may be executed repeatedly (#660)
- Drop Django 4.0 from CI to avoid security issues (#662)
- Change assert self.app.timezone.zone to assert self.app.timezone.key (#664)
- README.rst: Use git instead of zipfile for installing from Github (#670)
- Update supported Python & Django version in setup.py (#672)
- Update runtime.txt to include Django 5.0 (#681)
- README.rst: Crontab effect description (#689)
- Replace case.patching fixture with mockeypatch + MagicMock (#692)
- Upgrade GitHub Actions and PyPy 3.10 and Django 5.0 (#699, #705)
- Django v5.0: django.utils.timezone.utc alias --> datetime.timezone.utc (#703)


.. _version-2.5.0:

Expand Down
1 change: 1 addition & 0 deletions setup.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,7 @@ def _pyimp():
Framework :: Django :: 3.2
Framework :: Django :: 4.1
Framework :: Django :: 4.2
Framework :: Django :: 5.0
Operating System :: OS Independent
Topic :: Communications
Topic :: System :: Distributed Computing
Expand Down