From 989910b075d210ece18d290ca31aff340ae58c27 Mon Sep 17 00:00:00 2001 From: David Taing Date: Wed, 7 Oct 2026 20:10:39 +1100 Subject: [PATCH] Move the empty-string checks migration after the last one hosted applied #152's migration was timestamped 20260912133715 but merged after #154's 20260914080000 had already reached the hosted project, so supabase db push refuses it as out of order and the deploy fails before building. Renaming it to a later timestamp lets the push apply it normally, and keeps local replay order the same as hosted order. Hosted never applied the old name, so nothing there records it. --- ...ring_checks.sql => 20261007100000_add_empty_string_checks.sql} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename supabase/migrations/{20260912133715_add_empty_string_checks.sql => 20261007100000_add_empty_string_checks.sql} (100%) diff --git a/supabase/migrations/20260912133715_add_empty_string_checks.sql b/supabase/migrations/20261007100000_add_empty_string_checks.sql similarity index 100% rename from supabase/migrations/20260912133715_add_empty_string_checks.sql rename to supabase/migrations/20261007100000_add_empty_string_checks.sql