Commit graph

4 commits

Author SHA1 Message Date
sam
4047df8610
fix: always get the latest migration even when two are applied at the same time
without also ordering by migration_name, two migrations being applied at
the same time *can* (but won't always) result in the *earlier* migration
being returned as the latest one. as our migrations are not idempotent,
this causes the bot to crash on startup (and even if they *were*
idempotent, the code that inserts the new migration name into the
migrations table isn't)
2024-11-27 15:22:29 +01:00
sam
a50a8567dd
feat: import messages from go version 2024-10-28 23:42:57 +01:00
sam
56af787e57
fix: don't specify duplicate key_roles in guild repository, let PK API service read strings as numbers 2024-10-28 14:57:05 +01:00
sam
ff92c5f335
excise entity framework from all remaining code 2024-10-28 14:04:55 +01:00