nessi/NexaPG
1
0
Fork 0
Code Issues 20 Pull Requests Actions Packages Projects Releases 12 Activity

[NX-104] Add migration upgrade/downgrade verification in CI #10

New Issue
Closed
opened 2026-02-13 13:13:31 +00:00 by nessi · 1 comment
nessi commented 2026-02-13 13:13:31 +00:00
Owner
Copy Link

Goal

Guarantee Alembic migration safety before release.

Scope

  • CI step: upgrade to head, downgrade one step, re-upgrade.
  • Validate schema remains consistent.

Acceptance Criteria

  • Migration CI job is required and green.
  • Failed downgrade/upgrade blocks merge.
## Goal Guarantee Alembic migration safety before release. ## Scope - CI step: upgrade to head, downgrade one step, re-upgrade. - Validate schema remains consistent. ## Acceptance Criteria - Migration CI job is required and green. - Failed downgrade/upgrade blocks merge.
nessi added this to the v1.0 - Stability, Reliability & Security (P0) milestone 2026-02-13 13:13:31 +00:00
nessi added the P0 label 2026-02-13 13:13:31 +00:00
nessi added reference development 2026-02-14 15:03:26 +00:00
nessi commented 2026-02-14 15:36:27 +00:00
Author
Owner
Copy Link

Changes in commits: NX-104

Goal

Ensure migration changes are safe before merge/release by validating upgrade/downgrade roundtrips and resulting schema consistency.

Delivered Scope

  • Added dedicated CI workflow:
    • .github/workflows/migration-safety.yml
  • Added migration safety job that runs:
    • alembic upgrade head
    • alembic downgrade -1
    • alembic upgrade head
  • Added schema consistency verification:
    • pg_dump --schema-only before/after roundtrip
    • diff -u comparison
  • Added normalization to avoid false negatives:
    • filters dynamic \restrict / \unrestrict lines from dumps.

Acceptance Criteria

  • ✅ Migration CI job exists and is green when migrations are safe.
  • ✅ Failed downgrade/re-upgrade fails CI.
  • ✅ Schema mismatch after roundtrip fails CI.
  • ✅ Workflow is suitable to be marked as required status check to block merges on failure.

Notes

  • No runtime application behavior changed.
  • No additional DB migration required for this CI feature itself.
Changes in commits: NX-104 ### Goal Ensure migration changes are safe before merge/release by validating upgrade/downgrade roundtrips and resulting schema consistency. ### Delivered Scope - Added dedicated CI workflow: - `.github/workflows/migration-safety.yml` - Added migration safety job that runs: - `alembic upgrade head` - `alembic downgrade -1` - `alembic upgrade head` - Added schema consistency verification: - `pg_dump --schema-only` before/after roundtrip - `diff -u` comparison - Added normalization to avoid false negatives: - filters dynamic `\restrict` / `\unrestrict` lines from dumps. ### Acceptance Criteria - ✅ Migration CI job exists and is green when migrations are safe. - ✅ Failed downgrade/re-upgrade fails CI. - ✅ Schema mismatch after roundtrip fails CI. - ✅ Workflow is suitable to be marked as required status check to block merges on failure. ### Notes - No runtime application behavior changed. - No additional DB migration required for this CI feature itself.
nessi closed this issue 2026-02-14 15:36:27 +00:00
Sign in to join this conversation.
development
Branches Tags
Labels
Clear labels
P0
High priority
 P1
Medium priority
 P2
Low priority
No Label P0
Milestone
No items
No Milestone v1.0 - Stability, Reliability & Security (P0)
Projects
Clear projects
No project
Assignees
Clear assignees
nessi
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nessi/NexaPG#10
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?