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
{{ message }}
Repository navigation
Default supabase/cli version and has incompatible changes, easy to accidentally mis-use #269
but because the type generation changed between supabase v1.136.3 and latest v1.145.4 we got mis-matches such as
-export type Database = {+export interface Database {
and we didn't hard-code a version in our github action.
That made me think: how can we best make sure that
Type generation works across supabase cli versions or at least developers get notified when using different versions? Maybe you folks have ideas around this topic and maybe this should get discussed in the supabase/cli repo?
The github action uses the latest supabase cli version by default instead of an hard-coded old version
What do you think of e.g. using the current cli version by default or automatically updating the supabase cli version we are using here based on the supabase cli releases?
Activity
leomelzer commentedon Feb 25, 2025
I'm using
jqto keep the package-lock.json and Action versions in sync.Maybe someone finds this useful:
jgoux commentedon Apr 3, 2026
Hey 👋
This is now implemented in #405