From 3edce1cc046d7b6fbf1f764690e71964410a1aff Mon Sep 17 00:00:00 2001 From: Daniel Hiller Date: Thu, 17 Sep 2026 02:38:56 +0200 Subject: [PATCH] fix: Date the webhook scope migration after the one before it The file came in named 20260502000000, which sorts ahead of the TOTP attempt limit from August. Knex records migrations in the order it runs them, so the last row in the table is not the same on every instance: a fresh install runs both in name order and ends on the August one, while an instance that already had it runs only this one and ends here. Pro reads that last row to recognise which Community version it is upgrading from, and it can only carry one name per version. Renaming to a timestamp after the August migration makes the last row the same everywhere. The rename is safe while this is only a few commits old on master and in no tag. Anyone who pulled in that window and already ran it would see knex offer it a second time. --- ..._webhook.js => 20260917000000_add_scope_columns_to_webhook.js} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename server/db/migrations/{20260502000000_add_scope_columns_to_webhook.js => 20260917000000_add_scope_columns_to_webhook.js} (100%) diff --git a/server/db/migrations/20260502000000_add_scope_columns_to_webhook.js b/server/db/migrations/20260917000000_add_scope_columns_to_webhook.js similarity index 100% rename from server/db/migrations/20260502000000_add_scope_columns_to_webhook.js rename to server/db/migrations/20260917000000_add_scope_columns_to_webhook.js