fix(checks): resolve migration prefix collision and qa-seed compile break #287

Closed
David wants to merge 0 commits from chore/checks-workflow-13ddfabf into main
Owner

The check.yml gate failed at the migration-prefix uniqueness step: three concurrently-merged branches each picked prefix 051 (051_mileage_entries, 051_payments_amount_positive, 051_tax_rate_widen_column), and sqlx keys its _sqlx_migrations ledger on that prefix so a collision makes the applied version ambiguous (PMS-198). Renumber the two later-committed files to 052 (mileage) and 053 (tax_rate) by commit date, leaving 051_payments_amount_positive as 051, so apply order is preserved. Update the lone doc-comment reference in mileage_tracking/mod.rs to the new filename.

Past the prefix step, cargo check/clippy --all-targets also failed: src/modules/seed/qa.rs (the operator-triggered QA walkthrough seeder, server feature, in the default build) had not been updated when the project/time-tracking service mutations gained a trailing &AuditCtx argument (PMS-117) and CreateProjectRequest gained actual_end_date (PMS-361). Thread the existing AuditCtx::system(tid) context into create_project/create_project_phase/create_task/create_time_entry, build a system context from the tenant in the two lookup helpers (ensure_qa_work_type, ensure_qa_task_status), and set actual_end_date: None on both QA project specs (both projects are unfinished, so no real end date).

#PMS-377

The check.yml gate failed at the migration-prefix uniqueness step: three concurrently-merged branches each picked prefix 051 (051_mileage_entries, 051_payments_amount_positive, 051_tax_rate_widen_column), and sqlx keys its _sqlx_migrations ledger on that prefix so a collision makes the applied version ambiguous (PMS-198). Renumber the two later-committed files to 052 (mileage) and 053 (tax_rate) by commit date, leaving 051_payments_amount_positive as 051, so apply order is preserved. Update the lone doc-comment reference in mileage_tracking/mod.rs to the new filename. Past the prefix step, cargo check/clippy --all-targets also failed: src/modules/seed/qa.rs (the operator-triggered QA walkthrough seeder, server feature, in the default build) had not been updated when the project/time-tracking service mutations gained a trailing &AuditCtx argument (PMS-117) and CreateProjectRequest gained actual_end_date (PMS-361). Thread the existing AuditCtx::system(tid) context into create_project/create_project_phase/create_task/create_time_entry, build a system context from the tenant in the two lookup helpers (ensure_qa_work_type, ensure_qa_task_status), and set actual_end_date: None on both QA project specs (both projects are unfinished, so no real end date). #PMS-377
fix(checks): resolve migration prefix collision and qa-seed compile break
All checks were successful
E2E / Playwright against staging (pull_request) Successful in 2m0s
Check / fmt + clippy + compile + unit/doc tests (pull_request) Successful in 2m55s
Integration / integration tests (pull_request) Successful in 7m49s
Create release / Create release from merged PR (pull_request) Has been skipped
92f67adf19
The check.yml gate failed at the migration-prefix uniqueness step: three concurrently-merged branches each picked prefix 051 (051_mileage_entries, 051_payments_amount_positive, 051_tax_rate_widen_column), and sqlx keys its _sqlx_migrations ledger on that prefix so a collision makes the applied version ambiguous (PMS-198). Renumber the two later-committed files to 052 (mileage) and 053 (tax_rate) by commit date, leaving 051_payments_amount_positive as 051, so apply order is preserved. Update the lone doc-comment reference in mileage_tracking/mod.rs to the new filename.

Past the prefix step, cargo check/clippy --all-targets also failed: src/modules/seed/qa.rs (the operator-triggered QA walkthrough seeder, server feature, in the default build) had not been updated when the project/time-tracking service mutations gained a trailing &AuditCtx argument (PMS-117) and CreateProjectRequest gained actual_end_date (PMS-361). Thread the existing AuditCtx::system(tid) context into create_project/create_project_phase/create_task/create_time_entry, build a system context from the tenant in the two lookup helpers (ensure_qa_work_type, ensure_qa_task_status), and set actual_end_date: None on both QA project specs (both projects are unfinished, so no real end date).

#PMS-377
Owner

Superseded: the qa-seed compile fix + 051 migration-prefix de-duplication landed on main via #288 (kept 051_mileage_entries at 051, renumbered the two never-deployed migrations). Closing this duplicate.

Superseded: the qa-seed compile fix + 051 migration-prefix de-duplication landed on main via #288 (kept 051_mileage_entries at 051, renumbered the two never-deployed migrations). Closing this duplicate.
vas2000-work closed this pull request 2026-06-17 02:13:58 +02:00
David deleted branch chore/checks-workflow-13ddfabf 2026-06-17 12:25:04 +02:00
All checks were successful
E2E / Playwright against staging (pull_request) Successful in 2m0s
Required
Details
Check / fmt + clippy + compile + unit/doc tests (pull_request) Successful in 2m55s
Required
Details
Integration / integration tests (pull_request) Successful in 7m49s
Create release / Create release from merged PR (pull_request) Has been skipped

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/mokosh-server!287
No description provided.