Update to Django 6.0 (#267)

See:
https://www.djangoproject.com/weblog/2025/dec/03/django-60-released/
https://docs.djangoproject.com/en/6.0/releases/6.0/

The project was synced with Django's project scaffold via:

```
uvx --from django django-admin startproject gettingstarted && cd $_
uvx --from django django-admin startapp hello
// copy files from new template into existing guide and revert changes where needed
uv venv
uv pip install -r requirements.txt
uv run ./manage.py makemigrations
uvx ruff format --preview
// update Django version numbers in any stray docs URLs
```

GUS-W-17606286.

Author: edmorley

Procfile

@@ -2,6 +2,6 @@ web: gunicorn --config gunicorn.conf.py gettingstarted.wsgi
 
 # Uncomment this `release` process if you are using a database, so that Django's model
 # migrations are run as part of app deployment, using Heroku's Release Phase feature:
-# https://docs.djangoproject.com/en/5.2/topics/migrations/
+# https://docs.djangoproject.com/en/6.0/topics/migrations/
 # https://devcenter.heroku.com/articles/release-phase
 #release: ./manage.py migrate --no-input

gettingstarted/asgi.py

@@ -4,7 +4,7 @@
 It exposes the ASGI callable as a module-level variable named ``application``.
 
 For more information on this file, see
-https://docs.djangoproject.com/en/5.2/howto/deployment/asgi/
+https://docs.djangoproject.com/en/6.0/howto/deployment/asgi/
 """
 
 import os

gettingstarted/settings.py

@@ -1,13 +1,13 @@
 """
 Django settings for gettingstarted project.
 
-Generated by 'django-admin startproject' using Django 5.2.
+Generated by 'django-admin startproject' using Django 6.0.
 
 For more information on this file, see
-https://docs.djangoproject.com/en/5.2/topics/settings/
+https://docs.djangoproject.com/en/6.0/topics/settings/
 
 For the full list of settings and their values, see
-https://docs.djangoproject.com/en/5.2/ref/settings/
+https://docs.djangoproject.com/en/6.0/ref/settings/
 """
 
 import os
@@ -21,15 +21,15 @@
 
 
 # Before using your Heroku app in production, make sure to review Django's deployment checklist:
-# See https://docs.djangoproject.com/en/5.2/howto/deployment/checklist/
+# See https://docs.djangoproject.com/en/6.0/howto/deployment/checklist/
 
 # Django requires a unique secret key for each Django app, that is used by several of its
 # security features. To simplify initial setup (without hardcoding the secret in the source
 # code) we set this to a random value every time the app starts. However, this will mean many
 # Django features break whenever an app restarts (for example, sessions will be logged out).
 # In your production Heroku apps you should set the `DJANGO_SECRET_KEY` config var explicitly.
 # Make sure to use a long unique value, like you would for a password. See:
-# https://docs.djangoproject.com/en/5.2/ref/settings/#std-setting-SECRET_KEY
+# https://docs.djangoproject.com/en/6.0/ref/settings/#std-setting-SECRET_KEY
 # https://devcenter.heroku.com/articles/config-vars
 # SECURITY WARNING: Keep the secret key used in production secret!
 SECRET_KEY = os.environ.get(
@@ -40,7 +40,7 @@
 # Django has a debug mode which shows more detailed error messages and also means static assets
 # can be served without having to run the production `collectstatic` command. However, this
 # debug mode *must only be enabled in development* for security and performance reasons:
-# https://docs.djangoproject.com/en/5.2/ref/settings/#std-setting-DEBUG
+# https://docs.djangoproject.com/en/6.0/ref/settings/#std-setting-DEBUG
 # Debug mode will be automatically enabled when the project is run via `heroku local` (which
 # loads the environment variables set in the `.env` file, where `ENVIRONMENT=development`).
 # SECURITY WARNING: Don't run with debug turned on in production!
@@ -55,7 +55,7 @@
     # On Heroku, it's safe to use a wildcard for `ALLOWED_HOSTS`, since the Heroku router performs
     # validation of the Host header in the incoming HTTP request. On other platforms you may need to
     # list the expected hostnames explicitly in production to prevent HTTP Host header attacks. See:
-    # https://docs.djangoproject.com/en/5.2/ref/settings/#std-setting-ALLOWED_HOSTS
+    # https://docs.djangoproject.com/en/6.0/ref/settings/#std-setting-ALLOWED_HOSTS
     ALLOWED_HOSTS = ["*"]
 
     # Redirect all non-HTTPS requests to HTTPS. This requires that:
@@ -67,7 +67,7 @@
     #    app's `gunicorn.conf.py` for how this is done when using gunicorn.
     #
     # For maximum security, consider enabling HTTP Strict Transport Security (HSTS) headers too:
-    # https://docs.djangoproject.com/en/5.2/ref/middleware/#http-strict-transport-security
+    # https://docs.djangoproject.com/en/6.0/ref/middleware/#http-strict-transport-security
     SECURE_SSL_REDIRECT = True
 else:
     ALLOWED_HOSTS = [".localhost", "127.0.0.1", "[::1]", "0.0.0.0", "[::]"]
@@ -78,11 +78,11 @@
 # Several optional Django features that are present in the default `startproject` template have
 # been disabled since they are not used by this example app. To use them, uncomment the relevant
 # entries in `INSTALLED_APPS`, `MIDDLEWARE`, `TEMPLATES` and `urls.py`. See:
-# https://docs.djangoproject.com/en/5.2/ref/contrib/admin/
-# https://docs.djangoproject.com/en/5.2/topics/auth/
-# https://docs.djangoproject.com/en/5.2/ref/contrib/contenttypes/
-# https://docs.djangoproject.com/en/5.2/topics/http/sessions/
-# https://docs.djangoproject.com/en/5.2/ref/contrib/messages/
+# https://docs.djangoproject.com/en/6.0/ref/contrib/admin/
+# https://docs.djangoproject.com/en/6.0/topics/auth/
+# https://docs.djangoproject.com/en/6.0/ref/contrib/contenttypes/
+# https://docs.djangoproject.com/en/6.0/topics/http/sessions/
+# https://docs.djangoproject.com/en/6.0/ref/contrib/messages/
 INSTALLED_APPS = [
     # Use WhiteNoise's runserver implementation instead of the Django default, for dev-prod parity.
     "whitenoise.runserver_nostatic",
@@ -131,7 +131,7 @@
 
 
 # Database
-# https://docs.djangoproject.com/en/5.2/ref/settings/#databases
+# https://docs.djangoproject.com/en/6.0/ref/settings/#databases
 
 if IS_HEROKU_APP:
     # In production on Heroku the database configuration is derived from the `DATABASE_URL`
@@ -159,7 +159,7 @@
 
 
 # Password validation
-# https://docs.djangoproject.com/en/5.2/ref/settings/#auth-password-validators
+# https://docs.djangoproject.com/en/6.0/ref/settings/#auth-password-validators
 
 AUTH_PASSWORD_VALIDATORS = [
     {
@@ -178,7 +178,7 @@
 
 
 # Internationalization
-# https://docs.djangoproject.com/en/5.2/topics/i18n/
+# https://docs.djangoproject.com/en/6.0/topics/i18n/
 
 LANGUAGE_CODE = "en-us"
 
@@ -190,7 +190,7 @@
 
 
 # Static files (CSS, JavaScript, Images)
-# https://docs.djangoproject.com/en/5.2/howto/static-files/
+# https://docs.djangoproject.com/en/6.0/howto/static-files/
 
 STATIC_ROOT = BASE_DIR / "staticfiles"
 STATIC_URL = "static/"
@@ -207,15 +207,9 @@
 # https://whitenoise.readthedocs.io/en/latest/django.html#WHITENOISE_KEEP_ONLY_HASHED_FILES
 WHITENOISE_KEEP_ONLY_HASHED_FILES = True
 
-
-# Default primary key field type
-# https://docs.djangoproject.com/en/5.2/ref/settings/#default-auto-field
-
-DEFAULT_AUTO_FIELD = "django.db.models.BigAutoField"
-
 # Customise the default logging config, since by default full Django logs are only emitted when
 # `DEBUG=True` (which otherwise makes diagnosing errors much harder in production):
-# https://docs.djangoproject.com/en/5.2/ref/logging/#default-logging-configuration
+# https://docs.djangoproject.com/en/6.0/ref/logging/#default-logging-configuration
 # For more advanced logging you may want to try: https://django-structlog.readthedocs.io
 LOGGING = {
     "version": 1,

gettingstarted/urls.py

@@ -2,7 +2,7 @@
 URL configuration for gettingstarted project.
 
 The `urlpatterns` list routes URLs to views. For more information please see:
-    https://docs.djangoproject.com/en/5.2/topics/http/urls/
+    https://docs.djangoproject.com/en/6.0/topics/http/urls/
 Examples:
 Function views
     1. Add an import:  from my_app import views
@@ -24,6 +24,6 @@
     path("", hello.views.index, name="index"),
     path("db/", hello.views.db, name="db"),
     # Uncomment this and the entry in `INSTALLED_APPS` if you wish to use the Django admin feature:
-    # https://docs.djangoproject.com/en/5.2/ref/contrib/admin/
+    # https://docs.djangoproject.com/en/6.0/ref/contrib/admin/
     # path("admin/", admin.site.urls),
 ]

gettingstarted/wsgi.py

@@ -4,7 +4,7 @@
 It exposes the WSGI callable as a module-level variable named ``application``.
 
 For more information on this file, see
-https://docs.djangoproject.com/en/5.2/howto/deployment/wsgi/
+https://docs.djangoproject.com/en/6.0/howto/deployment/wsgi/
 """
 
 import os

hello/migrations/0001_initial.py

@@ -1,4 +1,4 @@
-# Generated by Django 5.2 on 2025-04-06 14:54
+# Generated by Django 6.0 on 2025-12-08 13:11
 
 from django.db import migrations, models
 

requirements.txt

@@ -1,4 +1,4 @@
-django>=5.2,<5.3
+django>=6.0,<6.1
 gunicorn>=23,<24
 dj-database-url>=3,<4
 whitenoise>=6,<7