Skip to content

Releases: craigds/django-fieldsignals

0.8.0

25 Dec 05:05
3368309

Choose a tag to compare

Bug Fixes

  • Skip virtual fields like GenericForeignKey to avoid errors (#28)
  • Avoid errors from model init in admin interface (#27)
  • Fix Django 6.0 compatibility

Improvements

  • Add type hints and py.typed marker for better type checking
  • Modernize packaging (switch to pyproject.toml)
  • Support Python 3.8-3.13 and Django 4.2/5.2/6.0

Improve support for newer djangoes

16 Aug 05:08

Choose a tag to compare

Supported djangoes are now 2.2, 3.1, 3.2

Improved `changed_fields` API

02 Jul 00:43

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

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

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

Choose a tag to compare

Test on django 2.0

0.3.0

26 Feb 03:00

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

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

Choose a tag to compare

  • Adds django 1.8 and 1.9 support
  • Proper tests for all supported versions