fix: rename duplicate migration 000035 to 000037

Browse Source

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.

...

This commit is contained in:

Matthew Meszaros

2026-05-25 11:43:14 +00:00

parent c790812207

commit 1317ea67d6

2 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

internal/infrastructure/db/migrations/000035_api_key_smart_limits.down.sql → internal/infrastructure/db/migrations/000037_api_key_smart_limits.down.sql

internal/infrastructure/db/migrations/000035_api_key_smart_limits.up.sql → internal/infrastructure/db/migrations/000037_api_key_smart_limits.up.sql