Hello,
So my vercel branches are connected to my supabase branches. Inside my application code the supabase clients use the publishable and secret keys for connecting to supabase. These publishable and secret keys are env vars on my vercel branch.
Like 3 hours ago my e2e tests started failing. It seems that new branches stopped applying publishable + secret keys to my vercel env and only started putting the legacy anon + service role keys?
I hope I'm not imagining this, has anyone experienced this too?
The user reports that their Vercel branches connected to Supabase branches are not receiving the expected publishable and secret keys as environment variables. Instead, only legacy anon and service role keys are being applied, causing e2e tests to fail. They are seeking confirmation and solutions from others who might have experienced the same issue.
What were the environment variables you were accessing inside of your application. Were you accessing the PUBLISHABLE_KEY and the SECRET_KEY or were using the old environment variables but the right values just happend to be pulled in i.e ANON_KEY and the SERVICE_ROLE_KEY?