feat: implement migration rollback scripts#310
Merged
RUKAYAT-CODER merged 1 commit intoApr 23, 2026
Merged
Conversation
- Add 6 migration files (001-006) covering users, courses, modules, lessons, enrollments, and the migrations tracking table - Each migration has a fully reversible down() method that is the exact inverse of its up() (drops tables, indexes, enum types) - Add MigrationRegistry to wire all migrations in dependency order - Fix getRegisteredMigrations() in MigrationService and RollbackService (previously returned empty array, making rollback non-functional) - Add rollbackByName() and rollbackToVersion() to RollbackService - Fix NOT_IMPLEMENTED specific-rollback endpoint in MigrationController - Add POST /migrations/rollback/to/:migrationName endpoint - Add migrate:run, migrate:status, migrate:rollback, migrate:rollback:count, migrate:rollback:to, migrate:reset npm scripts to package.json - Add docs/migrations.md with full usage, rollback, and env guidance
|
@Dennis-Ritchie1 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
Kindly fix CI |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements full migration rollback capability for Issue #299.
Changes
users,course,course_module,lesson,enrollment, and themigrationstracking tabledown()that is the exact inverse of itsup()— drops tables, indexes, and enum types in reverse ordermigration.registry.ts— central registry wiring all migrations in dependency ordergetRegisteredMigrations()inMigrationServiceandRollbackService(previously returned[], making rollback non-functional)rollbackByName()androllbackToVersion()toRollbackServiceNOT_IMPLEMENTEDspecific-rollback endpoint inMigrationControllerPOST /migrations/rollback/to/:migrationNameendpointmigrate:run,migrate:status,migrate:rollback,migrate:rollback:count,migrate:rollback:to,migrate:resetnpm scriptsdocs/migrations.mdwith full usage, rollback, and environment guidanceTesting
migrate:run→ verify schema → runmigrate:rollback→ verify schema restoredClose #299