fix: Date the webhook scope migration after the one before it

Browse Source

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.

...

This commit is contained in:

Daniel Hiller

2026-09-17 02:38:56 +02:00

parent 67d3ccf425

commit 3edce1cc04

1 changed files with 0 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

server/db/migrations/20260502000000_add_scope_columns_to_webhook.js → server/db/migrations/20260917000000_add_scope_columns_to_webhook.js