v2.19.1

Changed

• The MTI parent _updated_at trigger skips an ancestor this transaction already stamped (#84, ADR 0040). A full save() of a multi-table-inheritance child updates the ancestor first, so the follow-up UPDATE rewrote the row with the same value: two writes became one. A child-only update_fields save still stamps the ancestor. The change is a body replaced in place, CREATE OR REPLACE FUNCTION set_parent_updated_at(): no child table is migrated or locked, and the WHEN (pg_trigger_depth() = 0) stays.

Existing projects: run makemigrations (or makeguitarmigrations). It writes one migration in TRIGGER_FUNCTION_APP that replaces the function body; unapplying it puts the old body back.