I updated CI4 Database/MigrationRunner.php to fix all issues and add support migrations per module. The idea is to make the migration class supporting migration per module so that each module (Namespace) have it's own versioning sequence.
This will allow each module to be: added, updated, and deleted without affecting other modules. to explain the idea lets suppose that we have a website that we need to add a new chat module (migration number 9) to it and later we added a new blogging module to it (migration number 10).
After few months you decide to remove the chat module. With current migration strategy we can't use migration to delete the chat tables (9) as that we should first remove the blog tables (10).
As with my current solution every module could have its own migration sequence this problem is solved.
Please find attached my suggested file update for more information.
