I have a question regarding Django version 3.2.12.
When I change the DEFAULT_AUTO_FIELD to BigAutoField and create&apply migrations, the foreign keys of auto-generated through tables are dropped. This can be observed by running sqlmigrate which drops foreign key relations but never recreates them.
I noticed this is already fixed in Django 4.0.3 (Refs #32743 -- Fixed recreation of foreign key constraints when alter… · django/django@3d9040a · GitHub) but not in 3.2.x branch.
Can I expect this commit will in time be applied to Django 3.2.x branch? I would like to migrate to BigAutoField to be future-proof, but would prefer not to write migrations by hand.