v1.3.3a4

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 #217

Full Changelog: v1.3.2...v1.3.3a4

v1.3.3a3

django 4 and adds support for m2m clear.

What's Changed

• Django4.0 compatibility by @aymaneMx in #211
• Update Django version in setup.py by @Real-Gecko in #213
• Fix bug on Many-To-Many clear() (#171) by @AriAbr in #210

New Contributors

• @Real-Gecko made their first contribution in #162
• @aymaneMx made their first contribution in #211
• @AriAbr made their first contribution in #210

Full Changelog: v1.3.2...v1.3.3a3

v1.3.3a2

Django 4 support

v1.3.2

django 3.2, python 3.9-3.10 support

What's Changed

• Make models translatable and add Russian translation by @Real-Gecko in #162
• M2M changes now logged by @Real-Gecko in #163
• Added missing migration by @Real-Gecko in #164
• CI builds install explicit django version by @jheld in #166
• Add new Django/Python versions by @serl in #198
• use TransactionTestCase for asgi test by @jkarstens in #185
• Spelling fixes by @boxed in #196

New Contributors

• @Real-Gecko made their first contribution in #162
• @serl made their first contribution in #198
• @jkarstens made their first contribution in #185
• @boxed made their first contribution in #196

Full Changelog: v1.3.0...v1.3.2

v1.3.2a1 django 3.2 and py3.9-3.10 support

Thanks to all for your hard-work in fixing the compatibility story on newer versions of django and python, as well as your patience and persistence in lighting a fire to get this out.

#198 rolls up all of the fixes and is built upon #184 and #185 so as we can see, this was quite a group effort.

Thank you to @jkarstens @tian-yi and @serl for your contributions so far.

v1.3.2a1 is up on PyPI (you must check the releases page in order to see pre-releases), and in order for pip to grab it (CLI or requirements file), you must specify the version you're seeking to install, otherwise you'll get the latest stable release, which is behind this.

v1.3.2 proper will be released as soon as we get 👍 from the community.

v1.3.1a1

Adds Russian translation and additionalCRUDEvent event types. Thansk @Real-Gecko

v1.3.0

Same as v1.3.0a5

Notably, #138 #147 #154 , and support for django 3.1.

v1.3.0a5 (pypy3 fix)

Accidentally kept a tracemalloc import in the tests module, and apparently that is not available in pypy3! So, new version, but if you're not on pypy, you're fine with v.1.3.0a4 (or until we release officially).

v1.3.0a4

Adds ASGI support via #147 so RequestEvent will work on WSGI and ASGI. async views (async def, not async as in "asgi") are not explicitly tested at this time. The changes made were in the signal handler and the middleware (the middleware will function correctly in ASGI and WSGI -- it does not support async at this time, which django is fine with no matter what). Should your view be run via async, please test ahead of time and we should be able to support that use case (if things break).

v1.3.0a3

nothing "new" since v.1.3.0a2, but had forgotten to remove the django < 2.2 and py < 35 tests on travis. We support 2.2-3, and thus officially py35-38.