[abe-101]

Step 5: Django 5.2.18 → 6.0.9. Builds on #256 (now merged): DRF 3.15 and allauth 65.12 didn't support Django 6.

The diff is the one-line pin change. No code changes were needed.

Compatibility

• Every installed package declares support for Django 6.0. I checked each package's metadata, not just pip check.
• Production meets Django 6.0's requirements: Python ≥ 3.12 (on 3.12 since Run production on Python 3.12 #250) and PostgreSQL ≥ 14 (on 16.14). psycopg2 2.9.13 is still supported.

Verified

• Schema: makemigrations --check (all apps) reports no changes, and migrate --plan on an existing database has nothing to do.
• pytest: 128 passed, golden files included, with Django's 6.1 and 7.0 deprecation warnings treated as errors. Nothing in our code or our dependencies uses an API Django is about to remove.
• mypy is clean, and manage.py check reports no issues.
• Local production rehearsal. Clean Python 3.12 venv with only requirements.txt, production settings, and psycopg2 against local Postgres and Valkey:
  • a fresh migrate ran the whole chain; collectstatic and compress --force succeeded
  • gunicorn served home, the .ics feed (cold and cached), login, signup, admin login and static files, all 200
  • 15 Tishrei came out correct for 2026, 2027 and 2028
  • zero errors and zero deprecation warnings in the log

Next

Django 6.1 is blocked: django-celery-beat 2.9.0, its latest release, requires Django<6.1. The next steps are Python 3.13 and then the builder change for 3.14.