Next.js Sentinel
v15.0.0-canary.198
The release includes enhancements, fixes, and performance improvements related to Turbopack, server-side rendering, cache handling, and error handling, along with documentation clarifications and codebase upgrades.
Relevance to Netlify:
The enhancements to Turbopack and server-side rendering may impact Netlify's Next.js Runtime and build process. Improvements in cache handling and error layouts could also be relevant. Upgrading React might require compatibility checks with Netlify's systems.
v15.0.0-canary.197
The core changes include React upgrade and improvements in next-upgrade tool. There are also fixes related to dev server and dynamicIO. Misc changes involve Turbopack enhancements, optimizations, and bug fixes, along with improvements in tests and GitHub schema update.
Relevance to Netlify:
The React upgrade and next-upgrade improvements could impact how Netlify's Next.js Runtime handles React versions and upgrades. Fixing dev server issues is relevant for Netlify's deployment process. Turbopack enhancements and optimizations might impact Netlify's build performance and caching strategies. Test improvements and GitHub schema updates could affect Netlify's testing and documentation.
v15.0.0-canary.196
Next.js v15.0.0-canary.196 includes significant changes related to dynamicIO, Partial Prerendering Fallbacks (PPR), and cache handling. There are also improvements in error handling and documentation updates.
Relevance to Netlify:
The dynamicIO changes, PPR improvements, cache handling updates, and error message enhancements could impact the Netlify Next.js Runtime, build process, middleware handling, and documentation.
v15.0.0-canary.194
This release includes fixes for the edge runtime sandbox, a codemod related change, and updates to documentation.
Relevance to Netlify:
The fix for the edge runtime sandbox in pages/api could impact Netlify's Next.js Runtime as it deals with transforming Next.js build output into Netlify-compatible files. The documentation updates may also be relevant for Netlify's documentation if they cover changes in canary releases.
v15.0.0-canary.193
The release mainly includes a fix for the cache symbol and an update to the playwright dependency
Relevance to Netlify:
The fix for the cache symbol might indirectly impact Netlify's Next.js Runtime if it relates to caching strategies or mechanisms. The update to the playwright dependency might not have a direct impact on Netlify's systems.
v15.0.0-canary.192
Next.js v15.0.0-canary.192 introduces support for 'use cache' in route handlers using the Edge runtime and re-adds canary gates for certain experimental features.
Relevance to Netlify:
The addition of support for 'use cache' in route handlers using the Edge runtime is directly relevant to Netlify's Next.js Runtime, as it involves caching mechanisms that could impact performance. The re-addition of canary gates for experimental features could signal potential changes or updates that may require adjustments in Netlify's systems or documentation.
v15.0.0-canary.191
Next.js v15.0.0-canary.191 includes various core changes such as improvements in handling bad input, dynamic behavior, TypeScript version, time display, cache handling, ESLint v9 support, cacheLife profiles, and more. Additionally, there are miscellaneous changes related to performance enhancements and bug fixes in Turbopack, tests, and peer versions alignment.
Relevance to Netlify:
The core changes like handling bad input, cache handling updates, ESLint v9 support, and performance enhancements in Turbopack can directly impact Netlify's Next.js Runtime, build process, and edge functions. The TypeScript version specification and improvements in time display might influence Netlify's documentation updates. Overall, these changes are significant and require attention from Netlify's engineering team.
v15.0.0-canary.190
The key changes in this release include cache improvements related to CacheScopeStore and encoding binary cache keys as ucs-2 strings.
Relevance to Netlify:
The cache improvements can potentially impact Netlify's Next.js Runtime by optimizing caching mechanisms, improving performance, and possibly affecting build processes. Encoding binary cache keys can enhance cache key handling, which may have implications on build processes as well.
v15.0.0-canary.189
The release includes various fixes, upgrades, and documentation improvements, with changes in server packages, metadata route handlers, React upgrade, and documentation updates related to typos, deprecated libraries, and peer dependencies.
Relevance to Netlify:
The fixes, upgrades, and documentation improvements can be relevant to Netlify, especially the server package changes that might impact Netlify's Next.js Runtime and the documentation updates that could influence Netlify's documentation.
v15.0.0-canary.188
Next.js v15.0.0-canary.188 introduces support for 'use cache' in route handlers, ensures 'loadComponents' is called during 'next build' for route handlers, and improves error handling in the App router. Additionally, there are enhancements to the error digest test suite.
Relevance to Netlify:
The addition of support for 'use cache' in route handlers, calling 'loadComponents' during 'next build' for route handlers, and improving error handling in the App router are directly relevant to the Netlify Next.js Runtime and build process. These changes may impact how Next.js applications are handled and built on Netlify's platform.
v15.0.0-canary.187
This release includes fixes, tweaks, and documentation updates related to `getStaticProps`, `swrDelta`, `expireTime`, and some typo fixes. It also introduces minification of CSS files in Turbopack.
Relevance to Netlify:
The changes related to `getStaticProps`, `swrDelta`, and `expireTime` could impact Netlify's Next.js Runtime in terms of middleware handling and build processes. Documentation updates are relevant for Netlify's documentation. The addition of CSS minification in Turbopack could influence Netlify's build process for Next.js projects.
v15.0.0-canary.186
The key changes in this release mainly focus on handling source map requests for Turbopack client chunks, unflaking a test, and increasing retry duration for HMR fetch logging tests.
Relevance to Netlify:
The handling of source map requests for client chunks could impact Netlify's Next.js Runtime if it affects how the build output is transformed into Netlify-compatible files. The test improvements might indirectly benefit Netlify by ensuring more reliable features.
v15.0.0-canary.185
This version includes various core changes related to compilation, request store scope, hanging promises, custom app routes, cookies handling, and performance APIs usage. Additionally, there are some miscellaneous changes like typo fixes and restructuring of code.
Relevance to Netlify:
The core changes such as block compilation, request store scope, cookies handling, and performance APIs usage can impact Netlify's Next.js Runtime, build process, and edge functions. The documentation updates can also be relevant for Netlify's documentation.
v15.0.0-canary.184
This release includes improvements related to source map support, static indicator style, React codemod suggestion, prefetch request handling, and upgrading React version. Additionally, documentation updates and enhancements to Turbopack caching and backend cleanup are present.
Relevance to Netlify:
The source map support for server components/actions in the browser, static indicator style tweaks, and React codemod suggestion could impact Netlify's Next.js Runtime and documentation. The prefetch request handling changes might affect Netlify's build process. Updates to Turbopack caching and backend cleanup could require adjustments to Netlify's Next.js support.
v15.0.0-canary.183
The release includes changes related to server-side rendering, webpack stats.json support, cache APIs, and various codebase improvements.
Relevance to Netlify:
The move of WorkStore and ActionStore to /server/app-render, addition of cache-related APIs, and fixes for hot reloader middlewares could impact Netlify's Next.js Runtime and build process. The webpack stats.json support might require adjustments to Netlify's build process configuration.
v15.0.0-canary.182
The Next.js v15.0.0-canary.182 release includes several codemods, improvements to next-upgrade, and various fixes. Some changes relate to improving type checking and optimizations.
Relevance to Netlify:
The enhancements to next-upgrade, codemods, and type checking may impact Netlify's Next.js Runtime, requiring adjustments to compatibility handling or middleware. The improvements in patches installation could affect build processes and edge functions. Fixing URL errors and optimization changes might influence Netlify's documentation and performance optimizations.
v15.0.0-canary.181
This release includes improvements related to export workers and a fix for i686 next-swc build issues.
Relevance to Netlify:
The improvement in handling export workers could impact the Next.js Runtime in terms of build optimization and performance. The fix for i686 next-swc build issues is relevant for ensuring compatibility and stability of Next.js projects on different architectures, potentially impacting Netlify's build process for Next.js projects.
v14.2.15
This release includes bug fixes and new features related to Next.js image component, routing, and dynamic routes.
Relevance to Netlify:
The bug fixes and improvements in the image component, routing, and dynamic routes could impact Netlify's Next.js Runtime, especially in handling image optimization, routing behavior, and dynamic routes processing.
v15.0.0-canary.154
The release includes improvements related to Turbopack, HMR, example URLs, PWA docs, syntax fixes, and webpack middleware features.
Relevance to Netlify:
The improvements in Turbopack and HMR functionality could impact Netlify's Next.js Runtime and build process. Fixing example URLs and PWA docs could affect Netlify's documentation. Syntax fixes and webpack plugin features may require updates in Netlify's systems.
v15.0.0-canary.155
Next.js v15.0.0-canary.155 includes updates to experimental trace tracking, fixes for Windows errors, React upgrade, addition of a new package, improvements in handling responses and linting, updates to examples, and various documentation fixes.
Relevance to Netlify:
The update to experimental trace tracking and fixes for Windows errors may impact Netlify's Next.js Runtime. The React upgrade and adding new packages may require adjustments to Netlify's build process. Documentation fixes might influence Netlify's documentation updates.
v15.0.0-canary.156
The release includes fixes for examples, improvements related to Turbopack, and credits to contributors.
Relevance to Netlify:
The fixes for examples may indirectly impact Netlify's documentation on using and understanding Next.js features. The improvements related to Turbopack might affect the Netlify Next.js Runtime to enhance performance. Credits to contributors may not have a direct impact on Netlify's systems.
v15.0.0-canary.157
The release includes various fixes, updates to examples, documentation improvements, and miscellaneous changes. Notable fixes include issues related to Windows compatibility, content-type header matching, and startTime error on Android 9 with Chrome 74.
Relevance to Netlify:
The fixes related to compatibility, headers, and errors are relevant to Netlify's runtime and build processes. Updates to examples could impact documentation for users. Miscellaneous changes like build configurations and JavaScript compatibility might have implications on Netlify's systems.
v13.5.7
Next.js v13.5.7 includes bug fixes related to invalid fallback revalidate value and introduces Shared Revalidate Timings.
Relevance to Netlify:
The bug fixes in this release, especially related to revalidate values, may impact Netlify's Next.js Runtime and build process. Shared Revalidate Timings could also potentially affect caching strategies or performance optimizations in Netlify's systems.
v14.2.12
Next.js v14.2.12 includes bug fixes and improvements related to prefetching, chunking revalidate tag requests, ESLint compatibility, and preventing incorrect marking of requests.
Relevance to Netlify:
The bug fixes and enhancements in prefetching and chunking revalidate tag requests could impact the performance and caching strategies in Netlify's Next.js Runtime. The ESLint compatibility fix may affect Netlify's build process for TypeScript projects. Preventing incorrect marking of requests aligns with maintaining accurate routing and asset loading in Netlify deployments.
v15.0.0-canary.158
This Next.js release includes fixes for various issues and improvements in handling certain aspects of the application. It also addresses documentation errors and enhancements for better developer experience.
Relevance to Netlify:
The fixes and improvements related to TS plugin, chunk revalidate tag requests, dynamicIO experiment, and third-party integrations like Google Analytics can impact Netlify's Next.js Runtime and build processes. Documentation updates can help improve Netlify's documentation for Next.js projects.
v15.0.0-canary.159
Next.js v15.0.0-canary.159 includes upgrades, fixes, additions, and removals related to React, package memory leak, browser compatibility, route modules, and dependencies.
Relevance to Netlify:
The upgrades to React and the addition of browser compatibility polyfills may impact Netlify's Next.js Runtime and build process. The removal of dependencies may lead to adjustments in Netlify's build configurations.
v15.0.0-canary.160
The release includes upgrades to React, bug fixes related to actions and cache control, improvements to Turbopack, and documentation updates.
Relevance to Netlify:
The upgrades to React may impact compatibility with Netlify Next.js Runtime. Bug fixes for actions and cache-control are important for ensuring proper functionality. Improvements to Turbopack can influence build performance on Netlify. Documentation updates like the Nitrogen AIO loader can impact how developers work with next/image on Netlify.
v14.2.13
Next.js version v14.2.13 includes bug fixes related to cache-control, browser compatibility, memory leak, and startup error, with credits to contributors.
Relevance to Netlify:
The bug fixes in this release, especially the cache-control issue, are relevant to Netlify's Next.js Runtime, which handles transforming Next.js build output into Netlify-compatible files. Browser compatibility improvements are significant for Netlify's user base. Memory leak fixes are crucial for stability. The startup error on Android 9 could impact Netlify deployments. Credits indicate community contributions, which might impact Netlify's open-source collaboration.
v15.0.0-canary.161
The release includes various core changes like renaming directories, adding support for a new prop in next/image, and improving server actions handling. There are also updates in example usage, code refactoring, and documentation improvements.
Relevance to Netlify:
The renaming of directories could impact Netlify's Next.js Runtime if specific directory structures are assumed. The addition of a new prop in next/image might require updates in Netlify's documentation. Improvements in server action handling could affect Netlify's build process or edge functions for Next.js projects. Code refactoring could potentially introduce compatibility issues or optimizations for Netlify's systems.
v15.0.0-canary.162
This release includes improvements to server directive SWC transform, removal of unused Server IDs tracking, and relocation of dynamic APIs.
Relevance to Netlify:
The improvements to server directive SWC transform and dynamic APIs can affect Netlify's Next.js Runtime by potentially changing the output structure or middleware handling. Removal of unused Server IDs tracking can streamline the runtime performance. These changes may require adjustments in Netlify's build process or edge functions for Next.js projects.
v15.0.0-canary.163
This Next.js release includes updates related to error handling, experimental tracing, middleware features, and changes to the app directory setup tip. It also contains improvements to Turbopack functionality and documentation updates.
Relevance to Netlify:
The updates related to error handling, experimental tracing, and middleware features could impact the Netlify Next.js Runtime by potentially requiring adjustments to how errors are handled or how middleware features are supported. The changes in the app directory setup tip could impact Netlify's documentation. The Turbopack improvements might affect Netlify's build process for Next.js projects.
v15.0.0-canary.164
Next.js v15.0.0-canary.164 includes improvements related to codemod for Async Request API, manifest type definition updates, and middleware experimental trace case fix.
Relevance to Netlify:
The codemod for Async Request API could impact Netlify's Next.js Runtime as it may introduce changes in how asynchronous requests are handled, which needs to be aligned with Netlify's middleware handling. Updates to the manifest types can affect Netlify's documentation regarding Next.js build outputs and edge functions. Fixing the middleware experimental trace case is relevant for Netlify's Next.js Runtime as it involves middleware handling improvements.
v15.0.0-canary.165
This release includes fixes related to legacy env config with experimental tracing and updates to font data. It also addresses a typo in the example comment for fetch options.cache section and updates the handling of duplicate headers.
Relevance to Netlify:
The fix for legacy env config with experimental tracing could impact how Next.js runtime interacts with environment configurations, which could affect Netlify's Next.js Runtime and build process. Additionally, updates to font data might influence how fonts are managed in Next.js projects deployed on Netlify.
v15.0.0-canary.166
Next.js v15.0.0-canary.166 includes enhancements related to client error listeners, patch console organization, napi binding typing, remote image pattern support, and more.
Relevance to Netlify:
The improvements in client error handling, patch console organization, and image support could impact Netlify's Next.js Runtime. The napi binding typing enhancements might require adjustments in the Netlify build process for Next.js projects. The introduction of new features and changes in error handling may necessitate updates to Netlify's documentation.
v15.0.0-canary.167
This release includes improvements related to code formatting, documentation updates, and codebase refactoring. There are also changes related to SSR caching, experimental features, and third-party integrations.
Relevance to Netlify:
The core changes such as codebase refactoring may impact Netlify's Next.js runtime by potentially affecting middleware handling or build transformations. Updates to SSR caching and experimental features might require adjustments to Netlify's documentation or build processes. The third-party integration for GTM server-side tagging could be relevant for Netlify's edge functions or build optimizations.
v15.0.0-canary.168
This release includes minor changes such as documentation updates, refactorings, and improvements for Turbopack and SSR caching examples.
Relevance to Netlify:
The documentation updates and refactorings might indirectly impact Netlify's documentation or build processes. The improvements in Turbopack could potentially affect Netlify's Next.js Runtime.
v15.0.0-canary.169
This release includes support for React 18 in the Pages router, a cache-wrapper implementation with RSC serialization, updated TypeScript types for React APIs, and various fixes and improvements.
Relevance to Netlify:
The core changes, especially extending support to React 18 and cache-wrapper implementation, can impact Netlify's Next.js runtime for compatibility and performance. The updated TypeScript types may require adjustments in Netlify's documentation and build process.
v15.0.0-canary.170
The release includes an update to an example project to utilize the App Router.
Relevance to Netlify:
The update to the example project to utilize the App Router could indicate changes in routing implementation or best practices, which might impact Netlify's Next.js Runtime, documentation, or build process.
Relevant PRs:
v15.0.0-canary.171
The key change in this release is the update to make Dynamic APIs async, which is a breaking change.
Relevance to Netlify:
This change is significant as it introduces a breaking change, impacting how Dynamic APIs work asynchronously. Netlify's Next.js Runtime may need adjustments to accommodate this change and ensure proper functionality.
Relevant PRs:
v15.0.0-canary.172
The release includes various core changes related to server/client manifests, cache handling, dynamic IO, environment variables, and React upgrade. It also introduces improvements in handling prefetching, shadowing properties, and alias handling. Misc changes involve enhancements in Turbopack builds and PR testing.
Relevance to Netlify:
The core changes in this release, such as cache handling, dynamic IO, and React upgrade, could potentially impact Netlify's Next.js runtime, requiring adjustments to handle new features or changes. Improvements in prefetching, alias handling, and shadowing properties may affect Netlify's build process or edge functions for Next.js projects. The Turbopack build enhancements and PR testing adjustments in the misc changes might impact Netlify's optimization strategies and testing procedures.
v15.0.0-canary.173
This release includes improvements in dynamic API cases, auto rotation of Server Reference hash salt, fixes in examples and documentation, and enhancements in directive transform and React Strict Mode usage.
Relevance to Netlify:
The improvements in dynamic API cases and Server Reference hash salt rotation might impact the Next.js Runtime in handling middleware. Updates in examples and documentation may influence Netlify's documentation. Enhancements in directive transform and React Strict Mode usage could affect Netlify's build process for Next.js projects.
v15.0.0-canary.174
The release includes various core changes related to dynamic APIs, bug fixes, experimental updates, and upgrades. It also covers miscellaneous changes like documentation updates and build improvements.
Relevance to Netlify:
The core changes involving new dynamic APIs, bug fixes, and experimental updates could impact Netlify's Next.js Runtime by introducing new features, requiring adjustments to middleware handling, or affecting compatibility with Netlify's deployment platform. The upgrade of React version may also necessitate compatibility checks. The documentation updates might influence Netlify's documentation for Next.js projects, while the build improvements could affect Netlify's build process for such projects.
v14.2.14
Next.js v14.2.14 includes bug fixes and improvements related to response handling, metadata API routes, app router, prefetch bailout detection, externals, and next/image module.
Relevance to Netlify:
The bug fixes in response handling (#70082, #70649) can impact the Next.js middleware handling in the Netlify Next.js Runtime. The improvements in metadata API routes (#70508, #70647) and app router (#70646) might affect the runtime's transformation process. Changes in prefetch bailout detection (#70618) and externals (#70382) could influence Next.js e2e tests and build processes on Netlify.
v15.0.0-canary.175
This release includes bug fixes, improvements in app segment config parsing, dynamic params interpolation, `next/image` configuration, changes in SWR delta value, and enhancements related to static pages and dynamic APIs.
Relevance to Netlify:
The improvements in dynamic params interpolation and app segment config parsing could impact the Netlify Next.js Runtime by influencing middleware handling. Additionally, changes in `next/image` configuration might require adjustments in Netlify's build process for Next.js projects.
v15.0.0-canary.176
The release includes improvements related to pages directory support, metadata usage, dynamic APIs access, HMR invalidation, and compatibility with React 18.
Relevance to Netlify:
The changes related to pages directory support and dynamic APIs access could impact the Next.js Runtime in terms of middleware handling and transformations for Netlify compatibility. The fix for missing await in metadata usage might also affect runtime behavior. Compatibility with React 18 is essential for Netlify's projects. HMR improvements could enhance the build process for Next.js projects on Netlify.
v15.0.0-canary.177
This release includes various fixes and internal changes related to rendering, codemod, renaming of internal components, and handling image configurations.
Relevance to Netlify:
The separation of viewport rendering from metadata and fixes related to image handling could impact how Next.js output is processed and transformed by the Netlify Next.js Runtime. The codemod changes might influence compatibility with Netlify's build process for Next.js projects. The renaming of internal components might require updates in Netlify's middleware handling. Image configuration fixes could affect Netlify's handling of images in Next.js projects.
v15.0.0-canary.178
The release includes various core changes focused on improving caching, routing, error handling, and module ID mapping. There are also miscellaneous changes related to TurboPack, React 18 tests, and documentation updates.
Relevance to Netlify:
The core changes related to caching, routing, and error handling, as well as the addition of RSC module ID mapping, could impact Netlify's Next.js Runtime and build process. The updates related to TurboPack might require adjustments to Netlify's systems. Additionally, the documentation updates could be relevant for updating Netlify's documentation.
v15.0.0-canary.179
This release includes core changes related to server actions, cookies, and configuration validation. It also addresses unique 'key' prop warnings and runs Middleware within WorkStore. Additionally, there are example updates and miscellaneous changes like deleting an unreferenced file.
Relevance to Netlify:
The core changes related to server actions, cookies, and Middleware execution can impact the Netlify Next.js Runtime in terms of how it handles server-side logic and state management. The fix for 'key' prop warnings is crucial to prevent issues in Netlify's build process. The example updates might influence Netlify's documentation for with-styled-components. The deletion of unreferenced files could indirectly improve performance or maintenance.