We have opted to explicity set the app config setting so there should not be a migration generated. even if there is, there should be no change for users (unless of course they chose to run the previous migration generation request from django before this change, and that's _out of scope_ for this problem).
What's Changed
* fix: migration missing for field ID by aymaneMx in https://github.com/soynatan/django-easy-audit/pull/217
**Full Changelog**: https://github.com/soynatan/django-easy-audit/compare/v1.3.2...v1.3.3a4