db push --include-seed skips seed files when there are no pending migrations

[mfairley]

Bug report

Describe the bug

When running supabase db push --include-seed, seed files are not applied if there are no new (pending) migration files. The command outputs "Remote database is up to date." and exits without executing any seed SQL, even though --include-seed was explicitly passed.

To reproduce

1. Have a Supabase project with all migrations already applied to the remote database
2. Add or modify a seed file in supabase/seed.sql (or supabase/seeds/)
3. Run supabase db push --include-seed
4. Observe that the command reports the database is up to date and does not execute the seed file

Expected behavior

When --include-seed is passed, seed files should be evaluated and applied regardless of whether there are pending migration files. The flag explicitly signals intent to seed the database.

Actual behavior

Seed files are only pushed when there are also pending migration files to apply. Without new migrations, the seed step is skipped entirely.

Related

• supabase db push --include-seed doesn't actually run seed files #4670 covers a related bug where dirty seed files have their hash updated but their SQL is not actually executed

System information

• OS: macOS
• Supabase CLI version: 2.76.9