Skip to content

Releases: craigds/django-fieldsignals

Improve support for newer djangoes

16 Aug 05:08
Compare
Choose a tag to compare

Supported djangoes are now 2.2, 3.1, 3.2

Improved `changed_fields` API

02 Jul 00:43
Compare
Choose a tag to compare
  • BACKWARD INCOMPATIBLE : The changed_fields kwarg passed to signals now contains field names as keys, not the field instances themselves.
  • Dropped testing for old Django releases (now supported: 2.2.8+, 3.0.x)

Update python/django support

10 Jan 00:29
Compare
Choose a tag to compare
  • Drop support for python 2
  • Add support for django 3.0
  • Add support for python 3.8

Django 2.1 support

10 Jan 00:27
Compare
Choose a tag to compare
  • Added support for django 2.1
  • Drop support for django 1.10 and earlier

0.3.1

26 Feb 03:00
Compare
Choose a tag to compare

Test on django 2.0

0.3.0

26 Feb 03:00
Compare
Choose a tag to compare

Drop support for django 1.9. Test on django 1.10 and 1.11

0.2.3

23 Feb 19:17
Compare
Choose a tag to compare
  • Fix AppRegistryNotReady errors introduced in 0.2.2. Thanks @PetrDlouhy

0.2.0 - Support Django 1.8+

25 Jan 23:44
Compare
Choose a tag to compare
  • Adds django 1.8 and 1.9 support
  • Proper tests for all supported versions