fix(migrations): renumber duplicate 054 prefix to 055 (PMS-411) #303

Merged

vas2000-work merged 1 commit from fix/PMS-migration-054-prefix-collision into main

2026-06-18 00:39:14 +02:00

vas2000-work commented

2026-06-18 00:31:10 +02:00

Owner

Fixes PMS-411. main has two migrations/054_*.sql (PMS-394 054_time_entry_general_category from #297 and PMS-410 054_user_theme_prefs from #301). The duplicate numeric prefix breaks check-migrations (PMS-198) and the sqlx test/migrate setup, so main's Check job is red and every open server PR inherits the broken migration set.

Renumbers 054_time_entry_general_category.sql -> 055_time_entry_general_category.sql (the second to merge). Pure rename - sqlx::migrate!() globs the directory, the two migrations are independent DDL, and main CI has been red since the collision (gating deploys) so no environment has applied a 054 yet.

This unblocks the other open server PRs (which then still each need their own colliding migration renumbered: #299 054_scheduling_templates, #296 054_companies_tenant_name_unique, #295 054_tickets_tenant_team_idx, #268 051_project_default_due_business_days).

#PMS-411

Fixes PMS-411. main has two `migrations/054_*.sql` (PMS-394 `054_time_entry_general_category` from #297 and PMS-410 `054_user_theme_prefs` from #301). The duplicate numeric prefix breaks `check-migrations` (PMS-198) and the sqlx test/migrate setup, so main's Check job is red and every open server PR inherits the broken migration set. Renumbers `054_time_entry_general_category.sql` -> `055_time_entry_general_category.sql` (the second to merge). Pure rename - `sqlx::migrate!()` globs the directory, the two migrations are independent DDL, and main CI has been red since the collision (gating deploys) so no environment has applied a 054 yet. This unblocks the other open server PRs (which then still each need their own colliding migration renumbered: #299 `054_scheduling_templates`, #296 `054_companies_tenant_name_unique`, #295 `054_tickets_tenant_team_idx`, #268 `051_project_default_due_business_days`). #PMS-411

vas2000-work added 1 commit

2026-06-18 00:31:10 +02:00

fix(migrations): renumber duplicate 054 prefix to 055 (PMS-411)

E2E / Playwright against staging (pull_request) Successful in 1m38s

Details

Check / fmt + clippy + compile + unit/doc tests (pull_request) Successful in 2m47s

Details

Integration / integration tests (pull_request) Successful in 7m25s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

57aefe6f08

PMS-394 (time-entry general category, #297) and PMS-410 (user theme prefs, #301) each shipped a migrations/054_*.sql; merging both left main with two files at prefix 054. sqlx keys its ledger on the numeric version and check-migrations (PMS-198) rejects duplicate prefixes, so main's Check job went red and every open server PR inherited the broken migration set.

Renumber 054_time_entry_general_category.sql to 055_time_entry_general_category.sql (the second to merge). Pure rename: sqlx::migrate!() globs the directory so nothing references the filename, and the two migrations are independent DDL so order is irrelevant. Deploy-safe: main CI has been red since the collision (which gates deploys), so no environment has applied a 054 yet; a fresh apply runs 054_user_theme_prefs then 055_time_entry_general_category cleanly.

#PMS-411