v0.15.6

0.15.6 (2021-12-09)

Non-breaking changes

<timestamp>_init.sql and globals.sql are no longer generated by supabase init

They are now ignored, so there should be no breaking change. You can delete globals.sql, but you should keep init.sql if you have already set a remote database.

extensions.sql and seed.sql are now optional

They are no longer generated by supabase init, but it will be run if you have them.

Bug Fixes

• etc. etc. (3a3f20b)
• db branch delete: forbid deleting curr branch (d17ca22)
• start: handle supabase/postgres:14.1.0 scram (1185d8f)
• --host localhost (c44acfe)
• move globals.sql & initial schema to utils (2138139)
• update images (f61e7d0)
• update images (ea41e84)

v0.15.5

0.15.5 (2021-12-08)

Bug Fixes

• Apply extensions.sql before migrations (5a3db53)

v0.15.4

0.15.4 (2021-12-08)

Bug Fixes

• supabase init hang on windows (6b78950)

v0.15.3

0.15.3 (2021-12-04)

Bug Fixes

• Add supabase/postgres:14.1.0 for config.json (#91) (ebdb28d)

v0.15.2

0.15.2 (2021-12-02)

Bug Fixes

• Error conn busy on subsequent db remote set (20a3441)

v0.15.1

0.15.1 (2021-12-01)

Bug Fixes

• start: pull Studio image (59245bb)

v0.15.0

0.15.0 (2021-11-30)

BREAKING CHANGES

supabase/config.json

• Removed ports.pgMeta
• Added ports.studio (required)

supabase start

• Unexpose pg-meta
• Expose Supabase Studio

Features

• start: add Supabase Studio (b4042d1)

v0.14.1

0.14.1 (2021-11-30)

Bug Fixes

• Upgrade realtime image to v0.19.0 (#83) (b396cc0)

v0.14.0

0.14.0 (2021-11-30)

Features

• Add inbucket to local setup (#78) (ea01313)

v0.13.0

0.13.0 (2021-11-25)

BREAKING CHANGES

.gitignore must be updated

If you did supabase init with an older version of the CLI, it was:

# Supabase
**/supabase/.temp
**/supabase/.env
**/supabase/.globals.sql

It should now be:

# Supabase
**/supabase/.branches
**/supabase/.temp
**/supabase/.env

Updated commands

• supabase link -> supabase db remote
• supabase deploy -> supabase db push
• supabase db dump -> supabase db commit
• supabase db restore -> supabase db reset
• Removed supabase resolve

Database branches no longer tied to Git branches

Need to re-link with remote (deploy) database

If you linked your remote database (old term: deploy database) with supabase link, you need to re-link it with supabase db remote set.

Update supabase/config.json

We no longer use excludeSchemas. This may be added back in the future (with possibly different semantics).

Move supabase/.globals.sql to supabase/globals.sql

.globals.sql was previously gitignored, but we decided to commit it to accommodate custom roles.

Create an empty supabase/extensions.sql

Bug Fixes

• db commit: use migration name from args (ad98ca6)
• decouple GetCurrentBranch from git (2a116f0)
• init_migration_sql (a62bc33)
• update init_migration_sql (34c6ea9)

Features

• supabase db changes (a71844a)
• supabase deploy -> supabase db push (051ba8f)
• commit & reset (48b12d2)
• db branch, db switch (178e1f9)
• filter out noise from diff output (ff0ae0c)
• link -> remote (0c9e340)
• remove supabase resolve (1adcf57)
• update supabase start (78fd495)
• update init (dafb25e)