Skip to content

Conversation

@dereuromark
Copy link
Member

@dereuromark dereuromark commented Jan 29, 2026

Currently there is nothing in the output suggesting an action should be taken for the old table structure:

using migration table queue_phinxlog

+--------+-----------------+---------------------------------+
| Status | Migration ID    | Migration Name                  |
+--------+-----------------+---------------------------------+
| up     | 20240307154751  | MigrationQueueInitV8            |
| up     | 20250508121432  | MigrationQueueMemory            |
| up     | 20251119005411  | MigrationQueueIndexOptimization |
| up     | 20260129000000  | MigrationQueueOutput            |
+--------+-----------------+---------------------------------+

It would help if the user would be notified that there is sth to do.

Summary

  • Adds a warning in the migrations status command output when the migration tracking table is a legacy phinxlog table (e.g. queue_phinxlog), directing users to run migrations upgrade to switch to the unified cake_migrations table.

Show a warning in the status command output when the migration
table is a legacy phinxlog table, directing users to run
`migrations upgrade` to switch to the unified cake_migrations table.
@markstory markstory merged commit 8836d47 into 5.x Jan 31, 2026
14 checks passed
@markstory markstory deleted the status-legacy-warning branch January 31, 2026 00:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants