v0.2.1

Fix/post delete signal gets called twice for models in a foreign-key …

v0.2.0

Support cascade delete (#11)

* Add docs and support django5 and py312

* Add py312 to the test matrix

* Add badges for supported versions of python and django closes #6

* Add support for cascade delete by overriding Collector

This implementation in not complete because both parent and child needs to be "bulk tracked" in order for it to work

still needs to handle if the parent is not "bulk tracked"

* run linters

* Add compatibility with django3.2 and django4.0

* Add cascading for model delete

* bump version and add change log

* Fix changelog entry

v0.1.0

Add docs and support django5 and py312 (#9)

* Add docs and support django5 and py312

* Add py312 to the test matrix

v0.0.8

• post_create_signal(), post_update_signal(), and post_delete_signal() were not waiting for transaction to commit before sending signals.
  This was causing the signals to be sent before the object was actually created/updated/deleted, Causing a race condition.
  This has been fixed by using transaction.on_commit().
  This will ensure that the signals are sent after the transaction is committed.
• Add support for send_robust by using tracking_info_TrackingInfo(is_robust=True). is_robust=False by default.

v0.0.7

Fix post_create_signal duplication on objects.create()

v0.0.6

What's Changed

• Feat/add custom manager by @hassaanalansary in #2
• Update documentation and docstrings

Full Changelog: v0.0.5...v0.0.6

v0.0.5

Stop relying on queryset being ordered (#1)

* Stop relying on queryset being ordered

* bump version

* add changelog entry

Support delete operations

v0.0.4

Support model.delete and queryset.delete

Version 0.0.3

v0.0.3

Fix remove kwargs only from bulk_create and bulk_update

First Working Release

v0.0.2

Fix automatic upload to PyPi