4.17.0

Improvements

• Add pgtrigger.is_ignored to check if triggers are being ignored by @dablak in #217.

4.16.0

Changes

• Drop Python 3.9 support, add Python 3.14 support, add Postgres 18 support, add Django 6.0 support by @wesleykendall in #216

4.15.4

Fixes

• Fix use of core Django management command options (e.g. --skip-checks) when using manage.py pgtrigger by @wesleykendall in #214.

4.15.3

Changes

• Clarify docs on statement-level triggers and how pgtrigger.Composer works by @wesleykendall in #212.

4.15.2

Fixes

• Remove incorrect validation for using concretely-inherited fields in trigger conditions by @wesleykendall in #208.

4.15.1

Fixes

• Allow ID fields of foreign keys to be expressed in pgtrigger conditions by @wesleykendall in #206.

4.15.0

Improvements

• Added the pgtrigger.Composer trigger utility for writing conditional statement-level triggers by @wesleykendall in #204.
• Provide statement-level versions of pgtrigger.Protect and pgtrigger.ReadOnly by @wesleykendall in #204.

Fixes

• Fixes an assertion error that can happen during migrations by @wesleykendall in #204.

4.14.0

Changes

• Support better type annotations for the compiler and migrations module by @cjwatson in #200
• Support Django 5.2, drop Postgres 13 support by @wesleykendall in #203.

4.13.3

Changes

• Changed project ownership to AmbitionEng by @wesleykendall in #195.

4.13.2

Fixes

• Allow overriding of management command logger by @max-prtsr in #187.