Lorenzo

Perfect, great improvement to the existing documentation!

I think it's very much needed to find a solution for this, especially since querying foreign tables this way is documented as the recommended solution (https://supabase.com/docs/reference/javascript/select#query-foreign-tables). Perhaps some insights could...

@stipsan pretty awesome to hear you guys are using it on Sanity.io! I've actually released version 6.0.0 recently which improves compatibility with the most recent versions of `@sanity/client` and `next`....

@stipsan that would actually be great! The most recent releases were almost always due to a major dependency update, either on the `@sanity/client` side or the `next` side. I was...

@thdk thanks for the extensive answer! I think my original message was indeed incorrect, i'm creating a monorepo with multiple packages. I think you have to choose for either a...

Yeah i also played around a bit more with this setup and i'm running into the same issue as @acc-nicholas is mentioning. The `package.json` in the dist gets updated, however...

@fahslaj could you perhaps provide some insight in the recommended approach here? It feels like the `nx release` feature currently doesn't support a pretty standard publishing workflow: determining the next...

@fahslaj thanks for getting back to us! That's indeed what i ended up doing, however it did take some extra effort to only build the specific packages that are actually...

It's actually awesome work you guys have put into this new feature, i can already see it's a very useful tool for our team. Even though our workflow isn't fully...

@JamesHenry that's a good point to consider. However actually this is how `nx release` currently determines the new version when initiating a "breaking change" in the non-stable (`0.x.x`) version range....