Vercel sync and secret environment variable docs added
Documentation clarifies that syncing Vercel environment variables requires a new deployment, and introduces a one-way setting to hide secret values from the dashboard.
Managing environment variables between platforms can be an exercise in frustration when the synchronization triggers are not obvious. Documentation has been updated to clarify exactly how environment variables flow from Vercel, and how to lock down sensitive values.
The updated guides detail that environment variables are pulled from Vercel strictly before each build. To push an updated value into the system, a fresh Vercel deployment must be triggered, either by pushing a new commit or redeploying directly from the dashboard.
Additionally, a new section covers secret environment variables. Variables can be permanently marked as secrets during creation, which completely hides their values from the dashboard. This is a strict, one-way operation. Once marked as a secret, the setting cannot be undone, and updating it requires deleting and recreating the variable entirely. This provides clear guidance for teams handling sensitive API keys and tokens in the deployment pipeline.