Skip to content

fix: renumber duplicate migration 000444 to 000445#23229

Merged
kylecarbs merged 1 commit into
mainfrom
fix/duplicate-migration-000444
Mar 18, 2026
Merged

fix: renumber duplicate migration 000444 to 000445#23229
kylecarbs merged 1 commit into
mainfrom
fix/duplicate-migration-000444

Conversation

@kylecarbs
Copy link
Copy Markdown
Member

@kylecarbs kylecarbs commented Mar 18, 2026

Two migrations were merged with the same number 000444:

This collision causes golang-migrate to fail at runtime since it reads both files as the same version.

Fix: Rename 000444_chat_message_runtime_ms.{up,down}.sql000445_chat_message_runtime_ms.{up,down}.sql.

Closes coder/internal#1411

Two migrations were merged with the same number 000444:
- 000444_usage_events_ai_seats (merged first, keeps 000444)
- 000444_chat_message_runtime_ms (merged second, renumbered to 000445)

This fixes the duplicate migration number which causes golang-migrate to fail.
@kylecarbs kylecarbs enabled auto-merge (squash) March 18, 2026 15:25
@kylecarbs kylecarbs disabled auto-merge March 18, 2026 15:30
@kylecarbs kylecarbs merged commit a130a7d into main Mar 18, 2026
30 checks passed
@kylecarbs kylecarbs deleted the fix/duplicate-migration-000444 branch March 18, 2026 15:30
@github-actions github-actions Bot locked and limited conversation to collaborators Mar 18, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

flake: Test process crash - duplicate migration number 000444

3 participants