Affected version
Reports that share this version, grouped in one feed.
Concurrent getStaticPaths executions under the same dynamic segment perform unsynchronized read-modify-write on prerender-manifest.json. Non-atomic writes leave the file invalid JSON, causing persistent 500s across all routes in dev server.
Next.js 16.3.0-canary.97 dev server logs a Network URL that is immediately blocked for hot reload due to cross-origin restrictions because the resolved networkHostname is not included in the default allowedDevOrigins.
When `next build` supplies a cancellation signal to the telemetry POST request, the built-in five-second timeout is not applied. This allows stalled telemetry endpoints to block the build for far longer than intended (e.g., 20-45 seconds) because only the caller's signal is used, which normally does not fire during a local build.
In Telemetry.record(), the promise stored in this.queue is the result of chaining .then().catch().then() on the promise returned by submitRecord(). Because .then()/.catch() return new Promise objects and do not copy custom properties, the final promise never has the _controller property that submitRecord() attached to its returned promise. The line (prom as any)._controller = (prom as any)._controller is a no-op. Consequently, flushDetached() always sees item._controller as undefined, making the abort() call a silent no-op.