You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(gate): exclude base-tree renames from the migration collision recheck and harden the tsx shebang
Renaming an already-merged base migration (same number, e.g. a typo fix)
unioned both the old name (still live on main pre-merge) and the new name,
self-colliding even though the merged tree would only ever have one file at
that number. Now the PR's own removed/renamed-away base filenames are
subtracted from the live tree before the union.
Also harden scripts/check-migrations.mjs's shebang with --no-install so a
missing local tsx fails closed instead of npx silently fetching an
unverified package from the registry, per the security scanner finding.
it("REGRESSION: renumbering (renaming) this PR's migration to resolve a real collision does not leave a stale hold from the old filename", async () => {
5983
6032
// Before the fix, the stale previousFilename (the OLD number) stayed in prMigrationFilenames forever,
5984
6033
// colliding with an unrelated already-merged file at that old number and permanently re-holding a PR
0 commit comments