From 3380e487e5f23bab806ff2a8a9a4d50f0a8bd67d Mon Sep 17 00:00:00 2001 From: Bohan-J Date: Fri, 24 Jul 2026 15:28:26 +0800 Subject: [PATCH] docs(migrations): correct VCS index migration range in 216_vcs_integration comment (MUL-3772) After renumbering the VCS migrations to 216-221, the header comment still referenced the pre-renumber index range (214-218). The indexes now live at 217-221. Comment-only; no SQL change. Co-authored-by: multica-agent --- server/migrations/216_vcs_integration.up.sql | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/migrations/216_vcs_integration.up.sql b/server/migrations/216_vcs_integration.up.sql index f15f2be6e3..1892030e42 100644 --- a/server/migrations/216_vcs_integration.up.sql +++ b/server/migrations/216_vcs_integration.up.sql @@ -17,7 +17,7 @@ -- rows below in a single atomic statement). The inline UNIQUE / PRIMARY KEY -- constraints stay — they back the ON CONFLICT upsert targets in vcs.sql. -- Secondary indexes live in follow-up single-statement CREATE INDEX --- CONCURRENTLY migrations (214-218), which cannot share a file with these +-- CONCURRENTLY migrations (217-221), which cannot share a file with these -- CREATE TABLEs. CREATE TABLE IF NOT EXISTS vcs_connection (