v1.2.2b4

This includes an additional fix that (due to changes on the on commit handling on CRUDEvent creation, if there was an error and the logger tried to log it, it was possible that instance's repr/str would have included something that was already deleted (this is a consumer level issue), so now we will try/except on the logger and pass if we have an error (not wonderful for now, but easier to just do that and get the release out).

v1.2.2b3

Default fix on the changed_fields conditional (if no changed fields, not making a CRUDEvent), not to use the newer flow (you may turn on the newer flow with a new settings toggle), via PR #129

This is likely the last beta release for 1.2.2.

v1.2.2b2

Adds pluggable logging/auditing support (not just database, but could do logging, elasticsearch, etc). database is the default. This was on PR #124 thanks to @atakanarikan

changeset also includes from release v1.2.2b1, but for brevity not included here.

v1.2.2b1

Fix #106 from issue #97

v1.2.1

Same as v1.2.1rc1

v1.2.1rc1

Fixes #119 , all clients use the same code path, but now split DB users will have the bug fixed, so long as they adjust the db setting that the project exposes.

v1.2

django 3.0 support same as v1.2rc1

#120 is what this release brings.

v1.2rc1

#121 django 3.0 initial support (and drops py27 and django 1.11). django 1.11 on py3 may still work, and py2 may work, but we are moving forward (which we basically did with the support of django 2.0, but the code changes weren't hard).

v1.1.2rc2

Includes a further commit which is a bugfix for admin field logic when using a split easyaudit database.

Fix for #122 ; thank you to @xiaobosheng for helping review & test.

v1.1.2rc1

This is a release for support for #109

Once we see a little bit of traction with its use we will release v1.1.2 proper.

@steverecio Thanks for adding in support for #109