Opening this as a draft since I know this only applies to Django 3.2 and future releases
When running Django 3.2 with the DEFAULT_AUTO_FIELD set to BigAutoField a new
migration file is generated for the blacklist token table. This migration is
unapplied and will log the following warning during startup.
You have 1 unapplied migration(s). Your project may not work properly until you apply the migrations for app(s): blacklist.
Run 'python manage.py migrate' to apply them.
The Django 3.2 release note related to the BigAutoField can be found here.
Opening this as a draft since I know this only applies to Django 3.2 and future releases
When running Django 3.2 with the DEFAULT_AUTO_FIELD set to BigAutoField a new migration file is generated for the blacklist token table. This migration is unapplied and will log the following warning during startup.
You have 1 unapplied migration(s). Your project may not work properly until you apply the migrations for app(s): blacklist. Run 'python manage.py migrate' to apply them.
The Django 3.2 release note related to the BigAutoField can be found here.