daamsie
April 23, 2026, 12:26am
1
Is there plans to fix this?
Many integrations are best avoided until this is fixed and I see no updates from Vercel on steps taken to help us lock things down following the recent security incident.
1 Like
amyegan
April 23, 2026, 2:33pm
2
We’re working on it
Thanks for reporting, our integrations team is actively working on this feature but since it involves adding support for each third party, we can’t give an immediate ETA for when it will be enabled on the Doppler integration
In the meantime, the fastest workaround to de-sync is to use vercel env pull .env.temp to pull non-sensitive env vars into a file, then you can copy/paste them into the “add new environment variable” flow and mark as sensitive
This isn’t ideal since doppler will no longer …
and Jacob shared a temporary workaround