RepoJournal
Django @django
113 wires and counting

$ follow Django

Keep up with Django in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-09-04
stories 7
GitHub RSS Archive Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Django deprecation warnings switch to calendar-based names

By RepoJournal · Filed · About Django

carltongibson Natalia
2 people shipped this
carltongibson @carltongibson 3 cited Natalia @nessita 3 cited

Django renamed its deprecation warning classes to match the 2028 calendar-based versioning, with old names kept as aliases to avoid breaking third-party code.

Django started aligning its deprecation warnings with DEP 20's calendar-based versioning [1]. RemovedInDjango70Warning is now an alias of RemovedInDjango2028Warning, and RemovedInDjango71Warning has been renamed to RemovedInDjango2029Warning [2][3]. Existing warning filters and except clauses in third-party code keep working across the rename [2]. Docs were updated accordingly [4].

The djangoproject.com CVE generator now emits one CVE 5.1 credits entry per person instead of packing all names for a role into a single string [5]. Reporter and remediator names are each given their own credits entry, and optional reviewer and analyst fields have been added for the "remediation reviewer" and "analyst" types [6]. Downstream consumers can now attribute roles individually.

Action items

References

  1. [1] Refs #37293 -- Updated deprecation warnings for new release cycle (DEP 20) ↗ django/django
  2. [2] Refs #37293 -- Aliased RemovedInDjango70Warning to RemovedInDjango2028Warning. ↗ django/django
  3. [3] Fixed #37293 -- Renamed RemovedInDjango71Warning to RemovedInDjango2029Warning. ↗ django/django
  4. [4] Refs #37293 -- Updated deprecation docs for calendar-based warning names. ↗ django/django
  5. [5] Fixed #2749: Emitted one CVE credits entry per person. ↗ django/djangoproject.com
  6. [6] [checklists] Emitted one CVE credits entry per person. ↗ django/djangoproject.com

$ ls django/reviews/ # the step-back reads

the week in review Django ORM fix week and calendar versioning prep the month in review Django 6.1, four CVEs, and a parallel-test fix that kills flaky runs
Topics: Python Full archive →

Quick answers

What shipped in Django on September 4, 2026?
Django renamed its deprecation warning classes to match the 2028 calendar-based versioning, with old names kept as aliases to avoid breaking third-party code. In total, 5 commits and 2 pull requests landed.
Who contributed to Django on September 4, 2026?
2 developers shipped this update, including carltongibson and Natalia.
What were the notable Django updates?
Refs #37293 -- Updated deprecation warnings for new release cycle (DEP 20), Refs #37293 -- Aliased RemovedInDjango70Warning to RemovedInDjango2028Warning, and Fixed #37293 -- Renamed RemovedInDjango71Warning to RemovedInDjango2029Warning.
♥

$ log @django --recent

Django bumps minimum oracledb to 4.0.2 4 shipped Docs search fragments fixed, Benevity link restored 9 shipped Django prepares for calendar versioning with new version tuple support 21 shipped Django fixes two query regressions in ORM 17 shipped

$ log --all # elsewhere on the wire

Meta React Native adds Stable API guards to renderer attributed string FastAPI & Pydantic Pydantic fixes Mypy plugin crash, tightens datetime constraints

$ ls showcases/

Rails Laravel Node.js Go Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic OpenAI

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.