Bobbie Soedirgo

I think it's owned by `postgres` because of an erratic migrations setup - will look into this tmr

I couldn't reproduce the issue in this [repo](https://github.com/soedirgo/repro-join-typings) - here's the types I'm getting: If anyone can reproduce the issue, can you share the contents of your generated types (`database.types.ts`)?

@fenos is this ready to be merged?

Looks great! 👍I guess we don't need to include [Testinfra](https://github.com/supabase/postgres/blob/32e93b510517ecb87c77a6cbbddf358acf3f0e10/.github/workflows/testinfra.yml#L8C19-L8C19) tests since this should only affect PG stuff?

Update: PG17 has now been rolled out to all regions. You can do `CREATE SUBSCRIPTION` by upgrading to PG17 via Project Settings > Infrastructure, so closing this.

Checks are [failing](https://github.com/supabase/postgres/actions/runs/15247596162/job/42877067477?pr=1609#step:10:3866): ``` > Caused by: > feature `edition2024` is required > > The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this...

Can you try upgrading the CLI and the SDK? The generated types look outdated to me

Can you set up an example repo where we can replicate this? It's difficult to reproduce the problem otherwise.

How are you invoking the Supabase CLI? Can you try invoking it with `npx supabase@latest`? Also, can you check if the contents of `./supabase/.temp/postgres-version` is the same in both repos?...

I don't think we'll support using enums that way. What you can do instead is to stringify it: ```ts .from(`${CollectionNames.Group}`) ```