Conversation
…deployme…" This reverts commit b08e16b.
|
Notifying the following users due to files changed in this PR based on this repo's notify modifiers: @timneutkens, @ijjk, @shuding, @huozhi: |
|
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 |
|
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 |
…ert-88012-brooke/addAutomaticDeploymentId
…ert-88012-brooke/addAutomaticDeploymentId
…ert-88012-brooke/addAutomaticDeploymentId
…ert-88012-brooke/addAutomaticDeploymentId
…ert-88012-brooke/addAutomaticDeploymentId
…ert-88012-brooke/addAutomaticDeploymentId
…ert-88012-brooke/addAutomaticDeploymentId
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles: **432 kB** → **432 kB** ✅ -24 B81 files with content-based hashes (individual files not comparable between builds) Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
|
…ert-88012-brooke/addAutomaticDeploymentId
| if (config.deploymentId.length > 32) { | ||
| throw new Error( | ||
| `Invalid \`deploymentId\` configuration: exceeds maximum length of 32 characters. See https://nextjs.org/docs/messages/deploymentid-too-long` | ||
| ) | ||
| } |
There was a problem hiding this comment.
@brookemosby @mischnic can you provide some context on why this was added?
This hardcoded length limit breaks our setup and if this is mostly meant as "best practice" kind of nudge - could this be optionally disabled or made the limit configurable?
Not a hard requirement so removing in [response to request](#88958 (comment))
This feature is a requirement for prebuilt skew protection.
Currently when you deploy with prebuilt skew protection does not work, because there is no deployment id available to set in the environment.
This fixes that problem by: