You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Unlike before, when I push changes in the ./supabase folder, migrations are not being detected and applied to the preview branch in Supabase. In fact, in Github, the checks have been running non-stop for the past 40 mins. There are no logs in those checks so I have no way of knowing what is wrong.
To Reproduce
Steps to reproduce the behavior:
Run the diff command to create a migration file locally.
Push changes to github
Wait
Keep waiting
Expected behavior
This was working just fine yesterday. Changes get pushed, Supabase<->Github integration detects it and applies them to the preview branch.
Screenshots
System information
There is no command to run so I cannot run --create-ticket.
@sweatybridge There is no indication of a push in the Supabase dashboard. The last log is from yesterday's push. I think the GitHub check needs to pass for Supabase to trigger the application of the migrations.
Describe the bug
Unlike before, when I push changes in the
./supabase
folder, migrations are not being detected and applied to the preview branch in Supabase. In fact, in Github, the checks have been running non-stop for the past 40 mins. There are no logs in those checks so I have no way of knowing what is wrong.To Reproduce
Steps to reproduce the behavior:
Expected behavior
This was working just fine yesterday. Changes get pushed, Supabase<->Github integration detects it and applies them to the preview branch.
Screenshots
System information
There is no command to run so I cannot run
--create-ticket
.SERVICE IMAGE │ LOCAL │ LINKED
─────────────────────────┼──────────────────┼─────────────
supabase/postgres │ 15.1.0.103 │ 15.1.0.103
supabase/gotrue │ v2.158.1 │ v2.163.2
postgrest/postgrest │ v11.1.0 │ v11.1.0
supabase/realtime │ v2.30.34 │ -
supabase/storage-api │ v1.11.0 │ v1.13.0
supabase/edge-runtime │ v1.62.2 │ -
supabase/studio │ 20241106-f29003e │ -
supabase/postgres-meta │ v0.84.2 │ -
supabase/logflare │ 1.4.0 │ -
supabase/supavisor │ 1.1.56 │ -
The text was updated successfully, but these errors were encountered: