Describe the bug
supabase db push --include-seed detects changes to seed files, updates hashes but it doesn't actually run the seed files.
To Reproduce
Steps to reproduce the behavior:
- Modify a seed file
- Add a migration (seed changes don't seem detected without a migration -- another issue)
- run
supabase db push --include-seed and answer Y to prompt to update seed
- Check remote database, seed data is not updated
Expected behavior
The seed data on the remote database is updated
System information
- Version of OS: Darwin 25.1.0 arm64 arm
- Version of CLI: 2.70.5
- Version of Docker: Docker version 29.1.3, build f52814d
- Versions of services:
| SERVICE IMAGE |
LOCAL |
LINKED |
| supabase/postgres |
17.6.1.054 |
17.6.1.054 |
| supabase/gotrue |
v2.184.0 |
v2.184.0 |
| postgrest/postgrest |
v14.2 |
postgrest/postgrest:v14.2 |
| supabase/realtime |
v2.69.0 |
- |
| supabase/storage-api |
v1.33.2 |
v1.33.0 |
| supabase/edge-runtime |
v1.68.4 |
- |
| supabase/studio |
2025.12.23-sha-f3af2c3 |
- |
| supabase/postgres-meta |
v0.95.1 |
- |
| supabase/logflare |
1.27.3 |
- |
| supabase/supavisor |
2.7.4 |
- |
Describe the bug
supabase db push --include-seeddetects changes to seed files, updates hashes but it doesn't actually run the seed files.To Reproduce
Steps to reproduce the behavior:
supabase db push --include-seedand answer Y to prompt to update seedExpected behavior
The seed data on the remote database is updated
System information