Jourdan @ Scribe

@mschoettle @jheld I'm having no issues anymore, thanks! Despite of that, I'd really like to know if there's any projection on when 1.3.7 will be released i.e. not beta. It's...

Well, actually, I just faced the same issue @djch experienced. Tracked it down to the migration [0004](https://github.com/soynatan/django-easy-audit/blob/master/easyaudit/migrations/0004_auto_20170620_1354.py#L16). I saw a squashed 0004 migration there which should replace the original 0004,...

Production flow should actually work fine. The problem I'm having is with running tests on CI. Django creates a database from scratch and loads those migration files, even if not...

Interesting. I'll have it tested again tomorrow and bring a stack trace of how Django reaches that code. Thanks!

Didn't have time to trigger the error today, day was pretty packed. The fix is just to remove the squashed migrations, though. There's no need to keep them around once...

The operation that adds the index needs to be removed given that the name was added during index creation. IIRC, that's set at migration 0018.

I got the Django version like `import django; dj_vesion=django.__version__`. You can see I have the squashed migration there but the error is still happening. Now here you can see how...

@jheld Here it is. This will eliminate backwards compatibility issues for good: https://github.com/soynatan/django-easy-audit/pull/305

The Django version is 5.1. I run tests via Django's `test` management command. The `showmigrations` actually showed me the issue: ``` easyaudit [X] 0001_initial [X] 0002_auto_20170125_0759 [X] 0003_auto_20170228_1505 [X] 0004_auto_20170620_1354...

The version is the latest, `1.3.7b3`. Recreated the database from scratch, now it works fine, and the issue has vanished from CI, probably due to the squash migration. I was...