From 1317ea67d69cd008252f43b7a93085485d2f7d78 Mon Sep 17 00:00:00 2001 From: Matthew Meszaros Date: Mon, 25 May 2026 11:43:14 +0000 Subject: [PATCH] fix: rename duplicate migration 000035 to 000037 PR #10 added 000035_api_key_suffix and PR #11 separately added 000035_api_key_smart_limits, both targeting the api_keys table. golang-migrate refuses to load when two source files share a version number, so the backend container failed health checks in fresh stacks. Bumping api_key_smart_limits to 000037 keeps PR #10 in its original slot (it landed first) and matches the next free version after 000036_contact_categories. The two migrations touch different columns so apply order does not matter. --- ...smart_limits.down.sql => 000037_api_key_smart_limits.down.sql} | 0 ...key_smart_limits.up.sql => 000037_api_key_smart_limits.up.sql} | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename internal/infrastructure/db/migrations/{000035_api_key_smart_limits.down.sql => 000037_api_key_smart_limits.down.sql} (100%) rename internal/infrastructure/db/migrations/{000035_api_key_smart_limits.up.sql => 000037_api_key_smart_limits.up.sql} (100%) diff --git a/internal/infrastructure/db/migrations/000035_api_key_smart_limits.down.sql b/internal/infrastructure/db/migrations/000037_api_key_smart_limits.down.sql similarity index 100% rename from internal/infrastructure/db/migrations/000035_api_key_smart_limits.down.sql rename to internal/infrastructure/db/migrations/000037_api_key_smart_limits.down.sql diff --git a/internal/infrastructure/db/migrations/000035_api_key_smart_limits.up.sql b/internal/infrastructure/db/migrations/000037_api_key_smart_limits.up.sql similarity index 100% rename from internal/infrastructure/db/migrations/000035_api_key_smart_limits.up.sql rename to internal/infrastructure/db/migrations/000037_api_key_smart_limits.up.sql