supabase / cli / 32052857199
62%
develop: 62%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-6301-94158474812f7b491387a909f3168f8d3b20b2e3
DEFAULT BRANCH: develop
Ran
Jobs 1
Files 95
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 62.406%. Remained the same
32052857199

push

github

web-flow 
fix(cli): order migrations consistently (#6225)

## 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: https://github.com/supabase/cli/pull/6038

---------

Co-authored-by: avallete <andrew.valleteau@supabase.io>

5571 of 8927 relevant lines covered (62.41%)

6.65 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32052857199.1 95
62.41
 GitHub Action Run
Source Files on build 32052857199