From de9e90df45fa3522ab9d4e542392199cdda9f7b4 Mon Sep 17 00:00:00 2001 From: Dushyant Singh Hada Date: Tue, 30 Jun 2026 11:23:54 +0530 Subject: [PATCH] fix: resolve duplicate migration version 20 collision (#2294) Two PRs (#2193, #2200) merged ~2h apart each added a migration file numbered 0020, since each branch only saw one such file at CI time and neither was rebased against the other before merge. Renumbers 0020_pr_reviews.sql to 0021_pr_reviews.sql. TestMigrationVersionsAreUnique already existed and is correct; it didn't catch this because it only runs against each PR's branch state, not the merged result of both PRs together. --- .../migrations/{0020_pr_reviews.sql => 0021_pr_reviews.sql} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename backend/internal/storage/sqlite/migrations/{0020_pr_reviews.sql => 0021_pr_reviews.sql} (100%) diff --git a/backend/internal/storage/sqlite/migrations/0020_pr_reviews.sql b/backend/internal/storage/sqlite/migrations/0021_pr_reviews.sql similarity index 100% rename from backend/internal/storage/sqlite/migrations/0020_pr_reviews.sql rename to backend/internal/storage/sqlite/migrations/0021_pr_reviews.sql