Closed tomvanderlee closed 3 years ago
On django 3.2 it creates a migration to be BigAutoField. This fixes it.
Django cabinet had the same issue: https://github.com/matthiask/django-cabinet/issues/13
Thanks! 🎉
I've just uploaded v0.18.1 to PyPI containing this fix :)
Thanks for the quick response!
On django 3.2 it creates a migration to be BigAutoField. This fixes it.