pokemon/nuzlocke-tracker
1
1
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Fix duplicate Alembic migration revision ID f7a8b9c0d1e2
All checks were successful
CI / backend-lint (push) Successful in 9s
Details
CI / frontend-lint (push) Successful in 30s
Details

Browse Source 
Two migrations (add_game_id_to_boss_battles and add_naming_scheme_to_genlockes)
shared the same revision ID, causing multiple heads. Gave boss_battles migration
a new unique ID (g8b9c0d1e2f3) and chained it after the naming_scheme migration.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Julian Tabel
2026-02-14 13:14:24 +01:00
parent bb3794a276
commit 56d5fb4800
2 changed files with 15 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
.beans/nuzlocke-tracker-j02g--fix-duplicate-alembic-migration-revision-ids.md Normal file
View File

@@ -0,0 +1,11 @@
---
# nuzlocke-tracker-j02g
title: Fix duplicate Alembic migration revision IDs
status: completed
type: bug
priority: normal
created_at: 2026-02-14T12:13:08Z
updated_at: 2026-02-14T12:14:34Z
---
Two migration files share revision ID f7a8b9c0d1e2: add_game_id_to_boss_battles and add_naming_scheme_to_genlockes. Fix by giving one a new unique ID and chaining them sequentially.