Check compatibility of Django-related packages (django-phonenumber-field, django-recaptcha, etc.) with Django 6
Update uv.lock and rebuild Docker images
Run the test suite / smoke-test key flows (board pages, forms, auth/sign-in, recaptcha)
Resolve any deprecation warnings introduced under 5.2 that become errors in 6.0
Notes
Do not start until Django 6 is released (or confirmed available) and third-party packages we depend on advertise Django 6 support.
## Summary
Upgrade SCHA from Django 5.2 (LTS) to Django 6.
Current pin in `pyproject.toml`:
```
django>=5.2,<6
```
## Scope
- [ ] Bump Django dependency to `>=6.0,<7` (or whatever the supported range is at upgrade time)
- [ ] Review [Django 6.0 release notes](https://docs.djangoproject.com/en/6.0/releases/6.0/) and apply any required code / settings changes
- [ ] Check compatibility of Django-related packages (`django-phonenumber-field`, `django-recaptcha`, etc.) with Django 6
- [ ] Update `uv.lock` and rebuild Docker images
- [ ] Run the test suite / smoke-test key flows (board pages, forms, auth/sign-in, recaptcha)
- [ ] Resolve any deprecation warnings introduced under 5.2 that become errors in 6.0
## Notes
Do not start until Django 6 is released (or confirmed available) and third-party packages we depend on advertise Django 6 support.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Upgrade SCHA from Django 5.2 (LTS) to Django 6.
Current pin in
pyproject.toml:Scope
>=6.0,<7(or whatever the supported range is at upgrade time)django-phonenumber-field,django-recaptcha, etc.) with Django 6uv.lockand rebuild Docker imagesNotes
Do not start until Django 6 is released (or confirmed available) and third-party packages we depend on advertise Django 6 support.