From 0dbd557a7a1d2eebdb5a6f2c97bafa21daa99f36 Mon Sep 17 00:00:00 2001 From: Minseong Choi Date: Sun, 5 Jul 2026 04:31:45 +0900 Subject: [PATCH] fix(store): renumber discoverable-login migration 0013 -> 0014 A resource-cache migration (0013_resource_cache.sql) was merged onto main concurrently and also claimed version 0013. LoadMigrations rejects any duplicate migration version, so the app would refuse to boot with both files present. Renumber the discoverable-login migration to 0014. The two migrations touch disjoint objects (0013 ALTERs servers to add cached_* columns; this one CREATEs webauthn_discoverable_challenges), so their relative order does not matter, and the table name is unchanged -- no Go reference moves. Renaming a just-published migration is safe here because neither version has been applied to a persistent database yet: there is no schema_migrations row for version 13 to reconcile. This is a pre-application renumber, not a history rewrite of an already-applied migration. --- ...iscoverable_login.sql => 0014_webauthn_discoverable_login.sql} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename internal/store/migrations/{0013_webauthn_discoverable_login.sql => 0014_webauthn_discoverable_login.sql} (100%) diff --git a/internal/store/migrations/0013_webauthn_discoverable_login.sql b/internal/store/migrations/0014_webauthn_discoverable_login.sql similarity index 100% rename from internal/store/migrations/0013_webauthn_discoverable_login.sql rename to internal/store/migrations/0014_webauthn_discoverable_login.sql