From eff78a80f5b4959a6baf48baaa8538edbb480ae5 Mon Sep 17 00:00:00 2001 From: Chet Nichols III Date: Thu, 30 Jul 2026 21:30:06 -0700 Subject: [PATCH] fix(migration): restore the published loopback version The loopback preservation migration has been on `main` as `20260722120000`, so existing databases can already have that version and checksum in `_sqlx_migrations`. A merge race renamed it to the same `20260722120001` version now used by the newer BMC suppression migration. So, restore the loopback migration's original filename and leave the BMC migration at `20260722120001`. The SQL stays byte-for-byte identical, existing migration histories keep matching, and SQLx sees each version exactly once. Signed-off-by: Chet Nichols III --- ...back.sql => 20260722120000_preserve_machine_ipv6_loopback.sql} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename crates/api-db/migrations/{20260722120001_preserve_machine_ipv6_loopback.sql => 20260722120000_preserve_machine_ipv6_loopback.sql} (100%) diff --git a/crates/api-db/migrations/20260722120001_preserve_machine_ipv6_loopback.sql b/crates/api-db/migrations/20260722120000_preserve_machine_ipv6_loopback.sql similarity index 100% rename from crates/api-db/migrations/20260722120001_preserve_machine_ipv6_loopback.sql rename to crates/api-db/migrations/20260722120000_preserve_machine_ipv6_loopback.sql