Bug: Supabase integration uses outdated user email

I found a bug with supabase integration.

I have a supabase database I'd like to connect to. However:

Vercel does not see it, only offering to create a new DB.
Upon creating a new one, it does so in a different supabase workspace, under my old email address.

Note that:

I have removed the address from supabase entirely already.
I am using GitHub OAuth to log in to both supabase and vercel, with the same account.
The github account did have the old email until a few months ago. Now I only use the new email address everywhere - both in Vercel, GitHub, Supabase.

What I've tried:

I have refreshed my GitHub authentication in Vercel
I have logged in again, in hopes it would refresh my session / clear the cache

I've disconnected the supabase integration. Reconnecting it seemingly refreshes the email, but does not see existing projects or DBs. Upon visiting supabase, the page throws the following error:

1{"message":"{\"code\":500,\"error_code\":\"unexpected_failure\",\"msg\":\"Multiple accounts with the same email address in the same linking domain detected: default\",\"error_id\":\"82f1e000-b561-4389-862e-284b1a8f9388\"}"}

I have connected to the DB by specifying the variable manually.

Thanks for reporting this. I shared this info with the team so we can investigate. Glad to hear you found a temporary workaround with the manual variable value

Hey . I've heard back from our integrations team and contacts at Supabase. If you reach out to Supabase support they'll be able to get this sorted. You can share a link back to this conversation for context.

Thanks for letting us know about this, and for your patience while we investigated