Django-auditlog

Latest version: v3.0.0

Safety actively analyzes 630094 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 5

0.4.2

_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

- Models can be registered with decorators now

Fixes

- A lot, yes, [_really_ a lot](https://github.com/jjkester/django-auditlog/milestone/8?closed=1), of fixes for the admin integration
- Flush command fixed for Django 1.10

0.4.1

Improvements

- Improved Django Admin pages

Fixes

- Fixed multithreading issue where the wrong user was written to the log

0.4.0

Breaking changes

- Dropped support for Django 1.7
- Updated dependencies - _please check whether your project works with these higher versions_

New features

- Management command for deleting all log entries
- Added admin interface (thanks, crackjack)

Improvements

- Django: add 1.10 support

Fixes

- Solved migration error for MySQL users

0.3.3

Fixes

- fix `unregister` method
- `LogEntry.objects.get_for_objects` works properly on PostgreSQL
- Added index in 0.3.2 no longer breaks for users with MySQL databases

Important notes

- The `object_pk` field is now limited to 255 chars

0.3.2

New functionality

- Django: support 1.9

Improvements

- Enhanced performance for non-integer primary key lookups

0.3.1

Fixes

- Auditlog data is now correctly stored in the thread.

Page 4 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.