Django is switching from its eight-month release cadence to one feature release per year starting January 2028, aligning with Python's annual October releases and replacing the LTS distinction with a uniform one-year mainstream plus two-year security/data-loss support window. The issue also rounds up Django REST Framework 3.18.0 (dropping Django 4.2/5.0/5.1, adding 6.1 support), security-only Python patch releases fixing about 30 vulnerabilities, Wagtail 8.0rc1, PyPI freezing its HTML index API in favor of the JSON API, DSF and PSF governance news, DjangoCon US 2026 logistics, and several community articles and projects including django-msgspec and emojet.
Table of contents
NewsReleasesDjango Software FoundationDjangoCon USPython Software FoundationWagtail CMS NewsUpdates to DjangoDjango Fellow ReportsArticlesEventsVideosDjango Job BoardProjectsQuestions this post answers
When is Django switching to an annual release cycle?
Starting in January 2028, Django moves from its eight-month release cycle to one feature release per year, timed to match Python's annual October releases. The change also drops the LTS distinction: every release will get one year of mainstream support followed by two years of security and data-loss fixes. Nothing changes before then. Track Django's release cadence shift ahead of the 2028 switch on daily.dev.
What does Django REST Framework 3.18.0 change?
Django REST Framework 3.18.0 drops support for Django 4.2, 5.0, and 5.1 while adding Django 6.1 support, and it switches list-serializer errors (many=True) to a dict format. It also adds a @throttle_scope decorator for function-based views, unaccent support in SearchFilter, and nulls_distinct support for UniqueTogetherValidator. Developers upgrading DRF projects can follow breaking changes like this on daily.dev.
Why is PyPI freezing the HTML simple-index format?
PyPI is adopting PEP 833 to stop extending the HTML simple-index API with new metadata, redirecting future additions to the JSON API instead. Nothing breaks and no action is required for typical users; only mirror operators or bulk consumers relying on the HTML index should consider switching to the JSON API. Teams maintaining PyPI mirrors can watch packaging-ecosystem shifts like this via daily.dev.