fix(cli): order migrations consistently

[7ttp]

TL;DR

#6038 sorted migrations by version for db push and migration up but left three sibling consumers reading the same data in file name order.

what's broken?

• migration list renders 2 migrations as 3 rows, one version shown as both remote only and local only
• db pull flags an in-sync tree as a conflict and asks to repair the same version both reverted and applied
• db reset / db start / the shadow db replay migrations in the reverse of the order db push applies

why was it biting?

The database returns migrations sorted by version, the files come back sorted by filename, and the two disagree whenever one version starts another: 20260420010000_b sorts first by filename, second by version.
our earlier fix sorted only the list db push reads, so the rest kept comparing the two orders as if they matched...

fixed now by:

One shared version sorter applied at the list merge, the pull reconcile walk, and the two replay owners.

invoked as	before	now
migration list	3 rows for 2 migrations	2 paired rows
db pull	false conflict, contradictory advice	in-sync
db reset / db diff replay	reverse of db push	same as db push

ref:

• spotted while working on: fix(cli): order migrations by version #6038

[github-actions]

Supabase CLI preview

npx --yes https://pkg.pr.new/supabase/cli/supabase@6798385e0625c5c1b0641db5ed4ac9250d7bd555

Preview package for commit 6798385.

[7ttp]

thanks @avallete :) 💚

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 98d86e5983

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".