Releases: swisscom/cleanerversion
Doc updates
Support for Django 2.0
Cleanerversion now comes with support for Django 2.0.
For bugs or extension suggestions, please open an issue or a Pull Request right away.
Support for EOL versions of Django (1.9 and 1.10) has officially been dropped.
Bugfix release
Several bugs in the admin view are now fixed.
Credits to @rossmechanic for contributing the fixes.
Compatibility for Django 1.9, 1.10 and 1.11
With version 2 of CleanerVersion, we support the overhauled ORM that came with Django 1.9.
By taking over all existing tests, we ensured feature-equivalence with former versions of CleanerVersion.
Please note, that version 2.x of CleanerVersion supports Django 1.9+, but not Django 1.8 and below.
Have fun.
prefetch_related fix
Handle deferred fields
Previously, it was impossible to use only() or defer() on a QuerySet for a Versionable Model; doing so resulted in an infinite loop.
This has been corrected, and some documentation about the limitations of this were added (specifically, it is not possible to clone or restore a version that has been fetched with deferred fields).
Going stable
- Starting with this version of CleanerVersion, Django versions < 1.8 are not supported anymore
- Support for UUID fields -> Read the upgrade notes (here) regarding this CleanerVersion release!!
- Bugfix: Avoid overlapping versions upon version restore
- Bugfix: prefetch_related with historic versions of reverse FK objects
- PLUS: we're going stable starting with this version! :)
Fixes and Django standard adoption
This release includes mainly bugfixes in the Admin interface (see PRs #106, #109, credits to @dunkelstern) and in the behaviour when working with Many-to-Many-relationships to self (see PR #112, credits to @brki).
You'll also notice a change that allows usage of Versionable objects that is closer to the Django default behaviour, by using objects as filter lookup values (see PR #113 for details, credits to @brki).
Restoring versions from Admin and bugfixes
This release extends the integration of CleanerVersion to Django's Admin interface.
Also, there are numerous fixes, like:
- reverse foreign key clearing now triggers a clone on related objects
- heterogeneous models (versioned and non-versioned ones) are now less error-prone
Bugfix on restoring versions
Check database for latest version when restoring a version