supabase / cli / 32025481732
62%

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
32025481732

push

github

web-flow 
feat(cli): default database workflows to the bundled pg-delta engine (#6102)

Bundles `@supabase/pg-delta` and `@supabase/pg-topo` into the CLI and
makes the in-process engine the default for pg-delta-backed `db diff`,
`db pull`, and the declarative schema workflows (`db schema declarative
generate|sync`). The legacy edge-runtime implementation remains
available as an explicit `SUPABASE_USE_PG_DELTA_NEXT=false` opt-out;
there is no automatic fallback or runtime package download — a
next-engine failure propagates instead of silently switching
implementations.

This branch is reconciled with the TypeScript database-command port on
`develop`:

- shared database bootstrap owns shadow-database setup and receives the
complete local configuration, including database webhooks
- pgAdmin uses the native TypeScript differ-container path, while `db
diff --use-pg-schema` remains the sole Go delegation
- `--project-ref` resolution stays in the TypeScript command path and is
rejected for delegated modes that cannot honor it
- local diffs target the running local database, while migration and
declarative baselines use isolated shadow databases
- declarative flows repair missing extension prerequisites, scope schema
filters, and warn when unsupported object kinds would be omitted
- when a legacy declarative tree cannot converge on the next engine,
sync offers a staged recovery flow: it generates a next-compatible
export into a sibling `<declarative_schema_path>-next` directory (never
inside the active tree — trailing separators in the configured path are
normalized, and staging into or under the active directory is rejected)
and prints adoption commands built from the configured path
- both compatibility gates (shadow-load failure and plan-refuse) render
one shared recovery template: diagnosis, evidence, an explicit
do-not-apply hazard line, and the staged-upgrade commands carried as the
error suggestion — so a deliberate gate prints actionable guidance
instead of the... (continued)

5571 of 8927 relevant lines covered (62.41%)

6.65 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32025481732.1 95
62.41
 GitHub Action Run
Source Files on build 32025481732