supabase start fails

[IdellHeaney]

Describe the bug
supabase start can fail on a fresh local start when storage is enabled but no storage buckets are configured.

The command stops the containers and exits with:

Error status 400: {"statusCode":"403","error":"Unauthorized","message":"new row violates row-level security policy"}

To Reproduce

1. Use a local Supabase project with storage enabled.
2. Do not define any [storage.buckets.*] entries.
3. Ensure supabase/.temp/storage-migration exists and contains a non-empty value, for example:

custom-metadata

4. Run:

supabase stop --no-backup
supabase start

Expected behavior
supabase start should complete successfully. If no storage buckets are configured, startup should not fail while trying to seed or list buckets.

Additional context
Removing supabase/.temp/storage-migration or disabling storage avoids the failure.

[7ttp]

have seen an identical issue before, which was reproducible
will push up a fix!

Thanks for pointing it out again 💚🙌