When I install this package it has changes without migration files
llexical opened this issue · 1 comments
The fix is here: #60
However no ones merged it, can we get it in asap because this isn't really usable as a package in production without it.
This issue has been caused by the fact that the 3.2 upgrade changes the default auto-created primary key field. For more info: https://docs.djangoproject.com/en/4.0/releases/3.2/#customizing-type-of-auto-created-primary-keys
3.1 is out of support now, however, 2.2 would have the same issue which currently is in support until the end of March. PR: #63 should fix the issue for 2.2 and can be reverted after it's no longer in support.
If you are having this issue and are using 3.1, 3.1 is out of date and update to 3.2. It's not a scary upgrade in my experience (can't believe I didn't realize as I have done it several times ahahha).