mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-20 11:06:06 +00:00
aa77e21d4b
gen:pg-baseline rewrote the baseline with its cut at the newest migration on disk, so after a migration landed after the cut, running it moved the cut over that migration while Postgres installs created from the old baseline would still run it through the migrator. It now refuses while a migration follows the committed cut, names those migrations and the routine, and moves the cut only with --move-cut (lint:dialect keeps such a migration under the post-cut rules either way). check:pg-baseline stopped comparing SQLite triggers with POSTGRES_TRIGGERS once the baseline was frozen, so a trigger a later migration created on SQLite went unnoticed. The comparison now runs in both states, with advice that points at the migration when the baseline is frozen.