A Django app that keeps a log of changes made to an object.
change
field to be a json field. by @sum-rock in https://github.com/jazzband/django-auditlog/pull/407
USE_TZ=False
by @hramezani in https://github.com/jazzband/django-auditlog/pull/511
serialized_data
with F expressions by @hramezani in https://github.com/jazzband/django-auditlog/pull/544
AUDITLOG_CID_GETTER
is None
by @aqeelat in https://github.com/jazzband/django-auditlog/pull/565
ObjectDoesNotExist
in evaluation of object_repr
by @aleh-rymasheuski in https://github.com/jazzband/django-auditlog/pull/592
LogEntry
instance in post_log
signal by @ppmathis in https://github.com/jazzband/django-auditlog/pull/605
changes_display_dict
when model is missing by @ppmathis in https://github.com/jazzband/django-auditlog/pull/609
Full Changelog: https://github.com/jazzband/django-auditlog/compare/v2.2.1...v3.0.0
LogEntry.change
field type to JSONField
rather than TextField
. This change include a migration that may take time to run depending on the number of records on your LogEntry
table (#407)(#495)AuditlogHistoryField.delete_related
to False
by default. This is different from the default configuration of Django's GenericRelation
, but we should not erase the audit log of objects on deletion by default. (#557)JSONField
. The JSONField.encoder
is assigned to json.dumps
. (#489)AUDITLOG_INCLUDE_ALL_MODELS
is enabled. (#498)*_id
naming. (#525)USE_TZ=False
. (#511)LogEntry.changes_dict()
returns an empty dict instead of None
when json.loads()
returns None
. (#472)verbose_name
when model is not accessible. (508)serialized_data
with F expressions. (508)This release adds support for Django 3.0, and drops support for Python 2 and unsupported Django versions (most notably Django 1.11).
Overview of changes: https://github.com/jjkester/django-auditlog/pull/263
Added support for Django 2.0, along with a number of bug fixes.
Release notes to be added soon.
Fixes
As it turns out, haste is never good. Due to the focus on quickly releasing this version a nasty bug was not spotted, which makes this version only usable with Django 1.11 and above. Upgrading to 0.4.3 is not only encouraged but most likely necessary. Apologies for the inconvenience and lacking quality control.
Improvements
Fixes