-
Notifications
You must be signed in to change notification settings - Fork 486
docs(release): notes for v2.109.0 #5742
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| ## Supabase CLI v2.109.0 — 2026-06-30 | ||
|
|
||
| v2.109.0 moves migration commands to TypeScript with a critical fix for pipeline-incompatible SQL statements, adds `db reset --sql-paths` for CI workflows, and resolves several database operation bugs. | ||
|
|
||
| ### Highlights | ||
| - **Migration files with pipeline-incompatible statements now apply correctly** — `migration up`/`down` now handle `CREATE INDEX CONCURRENTLY`, `VACUUM CONCURRENTLY`, `REINDEX CONCURRENTLY`, `ALTER SYSTEM`, `CLUSTER` without failing. (#5671) | ||
|
|
||
| ### New features | ||
| - **`db reset --sql-paths`** — Override seed SQL patterns per-reset without editing `config.toml`. (#5691) | ||
|
|
||
| ### Bug fixes | ||
| - Declarative schema sync detects stale local Postgres images and suggests restart instead of silently generating broken migrations. (#5646) | ||
| - `db diff` no longer fails when `schema_paths` glob patterns match no files, enabling gradual adoption of declarative schema. (#5702) | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The #5702 change only skips empty Useful? React with 👍 / 👎. |
||
| - Fixed `db diff`, `db pull`, and `db schema push` crashing when `supabase/migrations` directory already exists (Windows OneDrive, etc.). (#5724) | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The #5724 fix changed directory creation in Useful? React with 👍 / 👎. |
||
| - Fixed `supabase functions serve` crashing with "name too long" error on Windows when runtime bootstrap is large. (#5712) | ||
| - Fixed `config push` failing when remote Storage config is missing the optional `databasePoolMode` setting. (#5729) | ||
|
|
||
| ### TypeScript port progress | ||
| - **Now served by the TypeScript shell:** `migration new`, `migration list`, `migration fetch`, `migration repair`, `migration up`, `migration down`. Behavior matches the Go CLI. (#5671) | ||
|
|
||
| --- | ||
|
|
||
| Plus 20 internal improvements and dependency updates. | ||
|
|
||
| **Full changelog:** https://github.com/supabase/cli/compare/v2.108.0...v2.109.0 | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For migrations that contain VACUUM statements, the #5671 implementation handles bare
VACUUM/VACUUM (...)vialegacyIsPipelineIncompatible, not aVACUUM CONCURRENTLYform;VACUUM CONCURRENTLYis not valid Postgres syntax. Publishing this highlight would tell users to expect or write an invalid SQL statement and misdescribe the fix, so it should sayVACUUMinstead.Useful? React with 👍 / 👎.