Updated environment variables not picked-up on new build

Help
1

I have a GITHUB_ID environment variable configured in Vercel. The value didn’t seem to work, so I updated it and retriggered a deployment with a new commit+push. However, when logging the full process.env I see that the old value remained. I have triggered a new deployment three times now, but the old value remains.

What am I doing wrong, here? This simply seems like a bug and I’m totally stuck.

Edit: Also removing the environment variable in the Vercel settings has no influence, the old value remains in the build. I’m NOT using the build cache.

4

Welcome to the Vercel Community! Happy to help you debug this.

Can you also check that GITHUB_ID is set for the correct environment (Production/Preview/Development)?

It’d also be helpful to understand:

  • What framework are you using (Next.js, etc.)?
  • Are you using any monorepo tools like Turborepo or Nx?
  • Does your GITHUB_ID value contain any special characters, especially a $ at the beginning
  • Could you share your deployment URL so we can investigate further?

As a temporary workaround, you could try renaming the variable (e.g., to GITHUB_CLIENT_ID) as some users have reported this forces the new value to be recognized.

Let us know how you get on.

5

Hello Pauline,

Thank you for your reply. So far I have:

  • made sure that GITHUB_ID is set for all environments (Production/Preview/Development)
  • made sure that GITHUB_ID is NOT linked exclusively to a certain project
  • made sure that GITHUB_ID doesn’t start with a $

As mentioned, I have also removed GITHUB_ID and run a deployment. This didn’t affect the result and the old value (Iv23liEfay44RS08p7np) was still the value in process.env.GITHUB_ID. I have re-add the environment variable with the new value Iv23li1DVKYIbTMRDh6j, but still the old value shows.

I’m using Next.js in a standard (not-mono) repo.

I have applied the temporary workaround, adding a new environment variable named GITHUB_CLIENT_ID with the new value (Iv23li1DVKYIbTMRDh6j) but this environment variable simply seems missing.

All used and expected values are rendered for debugging purposes. You can see my app over here: https://bonzai-proxy-chat.vercel.app
The source code (tiny as it is) is now also public: GitHub - kweij/bonzai-proxy-chat: ProNextJS Tutorial App

It seems that and old (first?) state of the environment variables lingers in the build process and is not updated after adding or changing them in the Vercel Dashboard.

Feel free to look around, it’s just a learning repo! Any help is appreciated :folded_hands:
Either I’m missing something very basic or something is actually broken.