-
Notifications
You must be signed in to change notification settings - Fork 30.3k
Prebuilt skew protection cleanup #88920
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: canary
Are you sure you want to change the base?
Conversation
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
| // Don't override NEXT_DEPLOYMENT_ID if it's already set by Vercel | ||
| // This prevents conflicts when Vercel manages deployment IDs internally | ||
| if (!process.env.NEXT_DEPLOYMENT_ID) { | ||
| process.env.NEXT_DEPLOYMENT_ID = id | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| // Don't override NEXT_DEPLOYMENT_ID if it's already set by Vercel | |
| // This prevents conflicts when Vercel manages deployment IDs internally | |
| if (!process.env.NEXT_DEPLOYMENT_ID) { | |
| process.env.NEXT_DEPLOYMENT_ID = id | |
| } | |
| // When runtimeServerDeploymentId is disabled, the config value is authoritative | |
| // and should override any pre-existing environment variable to ensure consistency | |
| // between this.deploymentId and process.env.NEXT_DEPLOYMENT_ID | |
| process.env.NEXT_DEPLOYMENT_ID = id |
When runtimeServerDeploymentId is disabled and process.env.NEXT_DEPLOYMENT_ID is pre-set, divergence between this.deploymentId and process.env.NEXT_DEPLOYMENT_ID causes client/server deployment ID mismatch
Clean-up un-used error & also allow for both user configured & vercel set deployment ids.