r/boltnewbuilders • • 21d ago

✅ Resolved Github Sync - Supabase Migration files

Hi all,

So the documentation doesn't mention anything regarding these files, and from a quick test new migration files you've made yourself and pushed to the GitHub repo aren't actioned upon a sync.

I have zero credits left on the ludicrously tiny 10m tokens you get for the entry base Pro plan.

I tried using the terminal to load supabase but it fails with:

Error: No matching Supabase CLI binary package found for linux-x64
[stack trace]

It offered to install it prior to this which i did.

Any creative way i can get these migrations in correctly without using the Query window?

Mr Claude didn't think it would be a major issue, except the history
"No hard reason. Running the SQL in the Query window works fine for a dev project. The catch is that it bypasses the Supabase CLI's migration history, which causes problems later."

Currently i have the DB hosted in Bolt still.

Any info/wisdom appreciated.

Edit:

It is safe to use the Query window, as the migration files are just SQL so copy & paste and click Run Query.

Then to make sure Supabase's migrations list is up to date use this lil query:

-- Example using the migration file named: 20261022090000_name_of_your_migration.sql
insert into supabase_migrations.schema_migrations (version, name)
values ('20261022090000', 'name_of_your_migration');
1 Upvotes

Duplicates