v5.0.1

What changed in 5.0.1

• Changed: exclusion-constraint ADD CONSTRAINT DDL is now preceded by DROP CONSTRAINT IF EXISTS, so adopting a pre-existing hand-written constraint of the same name applies cleanly instead of failing with 42P07. The standalone drop path also uses IF EXISTS.
• Fixed: renaming a table no longer drops and recreates the exclusion and temporal constraints it carries (the same normalization complex indexes already had).
• Changed: a name-only change to an exclusion constraint, temporal constraint, or temporal foreign key — including the implicit one when a table rename changes a default-derived name — now emits ALTER TABLE … RENAME CONSTRAINT instead of dropping and rebuilding. Dependent temporal foreign keys survive such renames untouched.
• Tests: the differ is now exercised against real model snapshots — generated as C#, compiled in-memory, and rebuilt exactly as dotnet ef migrations add does — guarding the whole feature set against snapshot round-trip churn.