Migrations revert in the wrong order when going to "0" #2695
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Milestone
Apply-Migration 0 unapplies in the wrong order. It starts with the oldest migration. The first should be last and the last should be first.
The text was updated successfully, but these errors were encountered: