Describe the bug
The Wheels 4.0 CLI migration commands appear to complete successfully, but most commands do not actually perform any migration-related action.
Only the following command works correctly:
The following commands:
wheels migrate up
wheels migrate down
wheels migrate info
display success messages but do not execute any actual migration behavior.
To Reproduce
Steps to reproduce the behavior:
- Create a Wheels application with migrations
- Run migrations using:
wheels migrate latest
- Verify migrations are applied successfully
- Try the following commands individually:
wheels migrate up
wheels migrate down
wheels migrate info
- Observe that:
- success messages are displayed
- no actual migration changes occur
- no migration information is shown
Expected behavior
All migration commands should execute their respective operations correctly:
wheels migrate up
- should run the next pending migration
wheels migrate down
- should rollback the latest migration
wheels migrate info
- should display migration status/information
Actual behavior
- Commands display success output
- No migration action is performed
- Database state remains unchanged
- info does not return expected migration details
Additional context
- The migration system itself appears to work correctly
- Migrations can be executed successfully through:
wheels migrate latest
- the Wheels migrator interface/UI
This suggests the issue is specific to the Wheels 4.0 CLI command handling or command routing for:
Possible cause
The CLI may not be correctly passing or mapping migration subcommands internally, causing commands to exit successfully without invoking the actual migration operations.
Screenshots

Desktop:
Describe the bug
The Wheels 4.0 CLI migration commands appear to complete successfully, but most commands do not actually perform any migration-related action.
Only the following command works correctly:
The following commands:
display success messages but do not execute any actual migration behavior.
To Reproduce
Steps to reproduce the behavior:
wheels migrate latestExpected behavior
All migration commands should execute their respective operations correctly:
wheels migrate upwheels migrate downwheels migrate infoActual behavior
Additional context
wheels migrate latestThis suggests the issue is specific to the Wheels 4.0 CLI command handling or command routing for:
updowninfoPossible cause
The CLI may not be correctly passing or mapping migration subcommands internally, causing commands to exit successfully without invoking the actual migration operations.
Screenshots

Desktop: