32275518476
62%

Ran 19 Aug 2026 04:23PM UTC

Jobs 1

Files 95

Run time 1min

Badge

Embed ▾

Committed 19 Aug 2026 04:14PM UTC coverage: 62.406%. Remained the same

Build # 32275518476

Build Type

push

github

Committed by

web-flow

Commit Message

fix(cli): run DROP INDEX CONCURRENTLY outside the migration transaction (CLI-2218) (#6276)

Fixes
[CLI-2218](https://linear.app/supabase/issue/CLI-2218/support-drop-index-concurrently-in-migrations).

The v2.109.0 fix for pipeline-incompatible statements (#5671, design
from #5156) classifies statements that cannot run inside a transaction
block and runs them standalone outside the migration batch. Its pattern
list covers `CREATE [UNIQUE] INDEX CONCURRENTLY`, `REINDEX …
CONCURRENTLY`, `VACUUM`, `ALTER SYSTEM`, and `CLUSTER` — but not `DROP
INDEX CONCURRENTLY`, which was missed. A migration containing one still
gets batched into the implicit transaction and PostgreSQL rejects it:

```
ERROR: DROP INDEX CONCURRENTLY cannot run inside a transaction block (SQLSTATE 25001)
```

This adds the missing `DROP INDEX CONCURRENTLY` pattern to
`legacyIsPipelineIncompatible` in the TS legacy shell, and mirrors it in
the Go sidecar's `isPipelineIncompatible` (`pkg/migration/file.go`),
which is still reachable through the remaining Go-delegated paths that
apply migrations (`db remote commit`, `db branch`). Reported by an
enterprise customer running `db push` on v2.111.0.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Coverage Stats

5571 of 8927 relevant lines covered (62.41%)

6.65 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	32275518476.1	19 Aug 2026 04:23PM UTC	95	62.41	GitHub Action Run

supabase / cli / 32275518476
62%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 32275518476

supabase / cli / 32275518476 62%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 32275518476

supabase / cli / 32275518476
62%

README BADGES
x