Next.js Sentinel
v15.0.4-canary.28
The release includes various improvements and optimizations related to Turbopack, cache handling, performance enhancements, and some documentation updates.
Relevance to Netlify:
The changes related to Turbopack, cache handling, and performance enhancements could impact Netlify's Next.js Runtime and build process. The documentation updates might require corresponding changes in Netlify's documentation.
v15.0.4-canary.27
The release includes improvements related to webpack worker exits, React upgrade, and metadata types support for exactOptionalPropertyTypes.
Relevance to Netlify:
The upgrade to React and the implementation of metadata types support can impact Netlify's Next.js Runtime and build process. These changes might require updates to ensure compatibility with Netlify's system.
v15.0.4-canary.26
The release includes changes related to fallback behavior with async metadata and prefetching, as well as a reversion of a previous webpack worker exit implementation.
Relevance to Netlify:
The changes related to fallback behavior and webpack worker exit could impact the handling of routes and dynamic content in Next.js applications deployed on Netlify. It might require adjustments in the Next.js Netlify Runtime to ensure compatibility with these changes.
v15.0.4-canary.25
This release includes various refactorings and documentation updates, along with improvements related to logging, server directives, and navigation digest alignment.
Relevance to Netlify:
The improvements in logging and server directives can impact Netlify's Next.js Runtime. Documentation updates might be relevant to Netlify's documentation. The refactorings could influence Netlify's build process or edge functions for Next.js projects.
v15.0.4-canary.24
This release includes improvements in image encoding efficiency for Next.js images, better module naming for improved searchability, and documentation updates related to inline CSS and upgrading from previous versions.
Relevance to Netlify:
The improvements in image encoding efficiency might affect the performance of Next.js applications deployed on Netlify. The documentation updates could impact Netlify's documentation for Next.js users, especially those upgrading from version 13 to 14.
v15.0.4-canary.23
This release includes improvements to the Link component, error overlay, server action redirects, and the addition of forbidden and unauthorized APIs. Additionally, there are various documentation updates and performance optimizations.
Relevance to Netlify:
The improvements to the Link component and error overlay could impact Netlify's Next.js Runtime by potentially requiring adjustments to middleware handling. The addition of forbidden and unauthorized APIs may also be relevant for Netlify's build process or edge functions for Next.js projects. Documentation updates could impact Netlify's documentation.
v15.0.4-canary.22
The key changes in this release include improvements related to environment variable loading and updates to Turbopack functionality.
Relevance to Netlify:
The display of where environments are loaded from can be relevant for debugging and configuration purposes in Netlify's runtime. Updates to Turbopack functionality could impact Netlify's build process for Next.js projects, potentially requiring adjustments.
v15.0.4-canary.21
The release includes various improvements and fixes related to caching, transpilation, HTML validity, Turbopack, and experimental features like CSS inlining.
Relevance to Netlify:
The improvements in caching, transpilation, and HTML validity can impact Netlify's build process and edge functions for Next.js projects. Changes in Turbopack and the experimental CSS inlining feature may require updates to Netlify's Next.js support. The fix related to the `next-size-adjust` meta tag can affect Netlify's runtime behavior with Next.js projects.
v15.0.4-canary.20
This release includes fixes and improvements related to Turbopack, custom servers with minimal node modules support, and documentation updates.
Relevance to Netlify:
The improvements in Turbopack and support for custom servers with minimal node modules could impact Netlify's Next.js Runtime and build process. Documentation updates might require adjustments in Netlify's documentation. The fixes and enhancements could potentially affect Netlify's systems and workflows.
v15.0.4-canary.19
The release includes a fix for a failed build in the Mongoose example due to an environment variable not being found.
Relevance to Netlify:
The fix for a failed build due to missing environment variables could impact Netlify's build process for Next.js projects if similar issues exist in the Netlify environment setup.
Relevant PRs:
v15.0.4-canary.18
The release includes various refactorings, bug fixes, and improvements related to error handling, webpack, Turbopack, and documentation.
Relevance to Netlify:
The refactorings in error handling and webpack, along with improvements in Turbopack and documentation, can impact the Netlify Next.js Runtime, build process, and documentation. Fixes for sourcemaps and unhandled rejections can also enhance build quality.
v15.0.4-canary.17
The key changes in this release focus on MDX and Turbopack optimizations, with adjustments related to experimental features and persistent caching.
Relevance to Netlify:
The changes related to MDX and Turbopack optimizations may affect Netlify's Next.js Runtime and build process, as they impact experimental features and caching mechanisms. These changes could require updates to ensure compatibility and optimization.
v15.0.4-canary.16
The release includes changes related to resolving MDX plugins string format and refactoring Turbopack's filesystem writes to an effect-based system.
Relevance to Netlify:
The resolution of MDX plugins string format might impact Netlify's Next.js Runtime in handling MDX plugins. The refactoring in Turbopack could influence Netlify's build process efficiency for Next.js projects.
v15.0.4-canary.15
This release introduces the ability to emit build errors for unknown cache kinds.
Relevance to Netlify:
The ability to emit build errors for unknown cache kinds could impact the build process or edge functions for Next.js projects on Netlify, as it may affect how caching is handled or how errors are surfaced during builds.
Relevant PRs:
v15.0.4-canary.14
The release notes for Next.js version v15.0.4-canary.14 mainly include refactoring related to turbopack
Relevance to Netlify:
The refactoring of turbopack modules might impact Netlify's Next.js Runtime, particularly if there are changes to how modules are resolved or handled. It could also affect Netlify's build process if there are changes to the way server actions are managed.
v15.0.4-canary.13
This release includes changes related to cache behavior, prefetching, and code organization, as well as some fixes and refactors.
Relevance to Netlify:
The changes related to cache behavior, prefetching, and code organization might impact Netlify's Next.js Runtime, especially in handling middleware and transforming build output. The refactors and fixes could influence Netlify's build process and edge functions for Next.js projects.
v15.0.4-canary.12
This release includes various fixes, enhancements, and refactorings, such as fixing a not found boundary prop, silencing a Sass warning, moving access token for Segment Prefetch, upgrading React, and improving terminal stack traces.
Relevance to Netlify:
The fixes and enhancements related to performance, errors, and warnings can impact Netlify's Next.js runtime and build process. The upgrade of React might require compatibility checks and adjustments in Netlify's codebase. The improvements in terminal stack traces can enhance debugging for Netlify developers.
v15.0.4-canary.9
This release mainly focuses on package upgrades, code refactoring, and example updates. There are some minor fixes and improvements related to server actions, error handling, and dependencies.
Relevance to Netlify:
The package upgrades and code refactoring may impact the Netlify Next.js Runtime and the build process for Next.js projects on Netlify. The server actions related changes could also affect how Next.js middleware handling is done.
v15.0.4-canary.8
The release includes minor updates and fixes related to paths and static indicators.
Relevance to Netlify:
The update to the path might impact Netlify's documentation if it changes the recommended way to set up a Next.js project. The fix for the static indicator could affect how Netlify handles static files in Next.js projects.
v15.0.4-canary.7
This release introduces various changes related to improving caching, compiler options, and network URLs, along with miscellaneous updates and bug fixes.
Relevance to Netlify:
The changes related to caching optimizations, compiler options, and network URLs could impact Netlify's Next.js Runtime and build processes. The updates to documentation and bug fixes might influence Netlify's documentation and edge functions for Next.js projects.
v15.0.4-canary.6
This release includes improvements related to handling console errors, adding new APIs, fixing localStorage access, upgrading React, and enhancing tree shaking and PostCSS usage.
Relevance to Netlify:
The addition of new APIs like expireTag and expirePath could impact the Netlify Next.js Runtime if these APIs are utilized in the build process. Fixing localStorage access is crucial for maintaining compatibility. Upgrading React may require adjustments to Netlify's build process or edge functions. Enhancements in tree shaking and PostCSS usage could affect build optimizations for Next.js projects on Netlify.
v15.0.4-canary.5
The key change in this release is the addition of cache control headers for static app routes.
Relevance to Netlify:
This change is relevant to Netlify as cache control headers can impact performance and caching strategies in the Netlify Next.js Runtime and the build process for Next.js projects. Ensuring proper cache control headers are set is crucial for optimizing content delivery and improving user experience.
Relevant PRs:
v15.0.4-canary.4
This release includes important fixes for path issues, server-source-maps scenarios, and error logging in the Edge runtime, which are crucial for Netlify's Next.js Runtime and build process.
Relevance to Netlify:
The fixes for path exports, server-source-maps scenarios, and error logging directly impact the handling of Next.js builds and middleware in Netlify's Next.js Runtime and build process. These changes ensure better compatibility and functionality within Netlify's systems.
v15.0.4-canary.3
This release includes various fixes, improvements in documentation, and performance enhancements, mainly related to core functions and example changes.
Relevance to Netlify:
The fixes and improvements in this release can indirectly impact Netlify's Next.js Runtime, especially if they involve caching, performance enhancements, or changes in directory structures like moving API pages. The documentation changes could also be relevant for updating Netlify's documentation.
v15.0.4-canary.2
This release contains a reverted change related to Turbopack and credits a contributor.
Relevance to Netlify:
The reverted change might indicate potential instability or issues with the Turbopack integration, which could affect Netlify's build process or runtime. Acknowledging contributors like @sokra is not directly relevant to Netlify's systems.
Relevant PRs:
v15.0.3
Next.js v15.0.3 includes various fixes, updates, and improvements related to server-side rendering, dynamic IO, error handling, React updates, and documentation enhancements.
Relevance to Netlify:
Several changes such as dynamic IO enhancements, error handling improvements, React updates, and documentation fixes can impact Netlify's Next.js Runtime, build process, and documentation. The updates related to sourcemaps, server actions, and dynamic tracking are particularly relevant.
v15.0.3-canary.9
This release includes bug fixes, improvements to prefetching, updates to font data, features related to turbopack, and various documentation updates.
Relevance to Netlify:
The bug fixes and improvements to prefetching can impact Netlify's Next.js runtime by potentially improving performance and stability. Updates to font data may affect Netlify's build process for Next.js projects. The features related to turbopack might require adjustments in Netlify's build process or edge functions. Documentation updates can impact Netlify's documentation.
v15.0.3-canary.8
The release includes improvements related to error handling, prefetching, and documentation updates, along with changes in the Turbopack module.
Relevance to Netlify:
The changes related to error handling, prefetching, and documentation updates can impact Netlify's Next.js Runtime, build process, and documentation. The Turbopack module changes might require adjustments in Netlify's systems if they interact with it.
v15.0.3-canary.7
The release includes significant core changes related to prerendering, prefetching, and Turbopack, as well as updates to webpack and debugging features.
Relevance to Netlify:
The core changes related to prerendering and prefetching can impact Netlify's Next.js Runtime by affecting how pages are generated and served. Additionally, Turbopack improvements and webpack updates may influence Netlify's build process for Next.js projects.
v15.0.3-canary.6
This release includes improvements in handling client chunk source maps, dynamicIO validation logic, turbopack optimizations, CLI exit codes, prefetch responses, loading bailout conditions, and documentation updates.
Relevance to Netlify:
The changes related to client chunk source maps, CLI exit codes, and prefetch responses can impact Netlify's Next.js Runtime, while the documentation updates may affect Netlify's documentation. The optimizations in turbopack might influence Netlify's build process for Next.js projects.
v15.0.3-canary.5
This release includes upgrades to React, a fix related to caching, and documentation updates.
Relevance to Netlify:
The upgrade of React could impact Netlify's Next.js Runtime and build process. The caching fix may also be relevant to how Netlify handles caching. Documentation changes may not directly impact Netlify's systems but could indirectly impact developers using Netlify.
v15.0.3-canary.4
The release contains improvements related to testing, performance, code refactoring, and documentation updates.
Relevance to Netlify:
The improvements in testing utilities, performance enhancements, and updates to code refactoring and documentation could impact Netlify's Next.js runtime, documentation, build process, and edge functions.
v15.0.3-canary.3
This release includes improvements related to caching, source mapping for Windows, documentation updates, and turbo tasks.
Relevance to Netlify:
The fixes for caching and source mapping can impact Netlify's runtime and build process. The documentation updates might require adjustments in Netlify's documentation. The turbo tasks improvements could influence Netlify's edge functions for Next.js projects.
v15.0.3-canary.2
This release includes various fixes, upgrades, and documentation improvements that might impact Netlify's Next.js Runtime and documentation.
Relevance to Netlify:
The fixes for redundant spaces, upgrading React, relaxing types, specifying supported Node.js versions, handling circular objects, and server component transformations may impact the Next.js Runtime of Netlify. Documentation updates for server-side debugging, middleware matching, and potential XSS vulnerabilities in router.push are relevant to Netlify's documentation. The alignment of property names, fix for cookie store, and upgrades may necessitate updates to Netlify's build processes or edge functions.
v15.0.3-canary.1
This release includes changes related to dynamic import/output updates, support for named pipes in .env files, and updates in examples and miscellaneous areas.
Relevance to Netlify:
The update related to dynamic import/output could impact Netlify's Next.js Runtime in terms of transformation handling. Support for named pipes in .env files might affect build processes. Changes in examples could be relevant for Netlify's documentation updates.
v15.0.3-canary.0
The release includes various fixes, updates to documentation, and minor improvements related to path updates, removing Turbotrace from webpack codepath, fixing relative redirects, exposing allowHeader, and URI encoding dynamic routes in the development environment.
Relevance to Netlify:
The updates to webpack codepath, relative redirects, and dynamic routes in the development environment could impact Netlify's Next.js Runtime and build process. The documentation changes also suggest potential updates needed in Netlify's documentation.
v15.0.2
The release includes various fixes, improvements, and updates related to dynamicIO, React upgrades, server-side rendering, error handling, and documentation enhancements.
Relevance to Netlify:
The improvements in dynamicIO, React upgrades, server-side rendering, and error handling can impact Netlify's Next.js runtime, build process, and edge functions, potentially requiring adjustments. Documentation fixes and enhancements are relevant to Netlify's documentation.
v15.0.2-canary.11
Next.js v15.0.2-canary.11 includes upgrades to React, improvements in handling sourcemaps, codemod enhancements, bug fixes for console colors and error printing, and documentation updates.
Relevance to Netlify:
The upgrades to React and improvements in sourcemap handling can impact Netlify's Next.js Runtime and build process. The bug fixes related to console colors and error printing are relevant for debugging on Netlify's platform. The documentation updates may impact Netlify's documentation.
v15.0.2-canary.10
The release contains several fixes and optimizations, default enabling of source maps in next dev, and updates to documentation.
Relevance to Netlify:
The optimizations and fixes could impact the performance and stability of Netlify's Next.js runtime. Default enabling of source maps could affect debugging in the runtime. Documentation updates might necessitate changes in Netlify's documentation for Next.js projects.
v15.0.2-canary.9
This release includes team changes, a codemod for turbopack, and credits to contributors.
Relevance to Netlify:
The team change might affect internal Next.js processes but is not directly relevant to Netlify. The codemod for turbopack could impact Netlify's support for Next.js projects if it changes build output or structure. The credits are not directly relevant.
Relevant PRs:
v15.0.2-canary.8
The release includes a change where experimental.instrumentationHook is no longer necessary.
Relevance to Netlify:
The removal of experimental.instrumentationHook might impact Netlify's Next.js Runtime if it was being used or considered for implementation. This change could require adjustments in Netlify's codebase or processes.
Relevant PRs:
v15.0.2-canary.7
The release includes various fixes related to stack frame color, fetch caching, hot-reloader-client, dynamic tracking, sourcemap errors, and trace uploads. Additionally, there are optimizations and code changes related to Turbopack.
Relevance to Netlify:
The fixes related to fetch caching and hot-reloader-client could impact Netlify's build process for Next.js projects. The changes around sourcemap errors might affect the debugging experience in Netlify's Next.js Runtime. The optimizations in Turbopack could potentially improve build performance in Netlify's systems.
v15.0.2-canary.6
This release includes updates related to prerender cache scoping and cache warming for validation.
Relevance to Netlify:
The changes in prerender cache scoping and cache warming can impact the way Next.js build output is handled and optimized in Netlify's Next.js Runtime. Netlify may need to adjust its build process or edge functions to accommodate these changes.
Relevant PRs:
v15.0.2-canary.5
This release includes improvements related to error handling during development and documentation updates.
Relevance to Netlify:
The changes related to error handling, logging, and documentation updates could impact the Netlify Next.js Runtime and documentation. The improvements in error handling might be relevant to Netlify's build process and edge functions for Next.js projects.
v15.0.2-canary.4
The release includes improvements related to error messages, dynamic imports, custom error callbacks for the app router, Webpack plugin simplification, and TurboPack enhancements.
Relevance to Netlify:
The enhancements in error messages, dynamic imports, custom error callbacks, and Webpack plugin simplification could impact the Netlify Next.js Runtime in terms of error handling, middleware processing, and build optimizations. The changes related to TurboPack might influence Netlify's build process for Next.js projects.
v15.0.2-canary.3
Next.js v15.0.2-canary.3 includes upgrades, experimental features, bug fixes, and improvements related to source maps and bundled runtime.
Relevance to Netlify:
The upgrade to React, enabling experimental build features, improvements in handling server component errors, and changes in source map paths for bundled runtime could impact Netlify's Next.js Runtime, build process, and edge functions.
v15.0.2-canary.2
This release mainly focuses on bug fixes and documentation updates, with improvements related to cache filling, dev overlay, and error messages.
Relevance to Netlify:
The bug fixes and improvements in cache handling and error messages could indirectly impact the Netlify Next.js Runtime and possibly the build process for Next.js projects. The documentation updates might influence Netlify's documentation.
v15.0.2-canary.1
This release includes updates to React, improvements in error handling, documentation updates, and a fix for a race condition in setting client reference manifests.
Relevance to Netlify:
The update to React versions could impact compatibility with Netlify's Next.js Runtime. Improvements in error handling may affect the way errors are managed in Netlify's deployment process. Documentation updates might require changes in Netlify's documentation. The race condition fix is relevant to stability in Netlify's build process.
v15.0.2-canary.0
The key changes in this release include improvements related to dynamic IO, server module map proxy, codemod enhancements, metadata image route normalization, Turbopack optimization, and documentation fixes.
Relevance to Netlify:
The improvements in dynamic IO, server module map proxy, and Turbopack optimization could impact Netlify's Next.js runtime in terms of performance, middleware handling, and build output transformation. Additionally, the documentation fixes are relevant to Netlify's documentation.
v15.0.1
Next.js v15.0.1 includes various core changes focusing on improvements, bug fixes, and updates. Key changes involve dynamicIO improvements, React upgrade, handling of server errors, CLI flag additions, and more.
Relevance to Netlify:
The improvements in dynamicIO, React upgrade, server action handling, and CLI additions could impact Netlify's Next.js Runtime, build process, and edge functions. The bug fixes related to server errors and package resolving might require adjustments in Netlify's systems.
v15.0.1-canary.3
The release includes fixes, improvements to dev overlay and setup dev bundler, new CLI flag --turbopack, and enhancements in dynamicIO for metadata detection. Additionally, updates for compatibility with Next.js 15 and some documentation fixes were made.
Relevance to Netlify:
The fixes and improvements in dev overlay and setup dev bundler could impact the Netlify Next.js Runtime. The addition of the --turbopack flag may affect Netlify's build process or edge functions for Next.js projects. Updates for compatibility and documentation fixes could influence Netlify's documentation.
v15.0.1-canary.2
Next.js v15.0.1-canary.2 includes fixes for handling terminal color in Chrome console, updating prerender functionality, improving dynamic navigations error handling, updating to ESLint v9 by default, preventing router errors from logging on the client, and addressing various other fixes and improvements.
Relevance to Netlify:
The updates related to handling terminal color, dynamic navigation errors, ESLint version change, and prevention of router errors logging are relevant to Netlify's Next.js Runtime for improving error handling and console output. The changes in middleware asset URLs and module resolution impact build processes and edge functions for Next.js projects hosted on Netlify.
v15.0.1-canary.1
The release includes core changes related to memory leak prevention, React upgrade, error logging improvement, and server action optimization. Misc changes include documentation updates.
Relevance to Netlify:
The core changes such as memory leak prevention, React upgrade, and server action optimization could impact Netlify's Next.js Runtime and build process. Improvements in error logging could also influence debugging and monitoring in Netlify's systems. Documentation updates might warrant updates to Netlify's documentation.
v15.0.1-canary.0
The release mainly includes changes related to dynamic imports, next-upgrade, next-codemod, and memory leak prevention.
Relevance to Netlify:
The improvements in dynamic imports handling and memory leak prevention could impact Netlify's Next.js Runtime and build processes. The next-upgrade changes might affect Netlify's documentation and recommended upgrade processes for users.
v15.0.0-canary.204
This release introduces minor changes related to code consistency and documentation, without major feature updates.
Relevance to Netlify:
The changes in this release are primarily related to code consistency (prompt wording) and documentation enhancements (image formats with next/image). While not directly impacting the Netlify Next.js Runtime or build process, improving documentation can indirectly benefit Netlify's users by providing more clarity on using next/image.
v15.0.0-canary.203
Next.js v15.0.0-canary.203 includes improvements in dynamic imports, caching, error handling, and TypeScript autocomplete. It also enhances worker cleanup and tracing for Turbopack.
Relevance to Netlify:
The improvements in cache functionality, error handling, and worker cleanup could impact Netlify's Next.js Runtime and build process. TypeScript autocomplete enhancements might influence Netlify's documentation. Changes in how dynamic imports are handled could affect Netlify's edge functions for Next.js projects.
v15.0.0-canary.202
This release primarily includes bug fixes and documentation corrections, with no significant feature enhancements or changes.
Relevance to Netlify:
The bug fix related to cache handlers in serialized config may have implications for Netlify's Next.js runtime, but without detailed context, its impact cannot be accurately assessed. The documentation correction might indirectly benefit Netlify's documentation, albeit minimally.
Relevant PRs:
v15.0.0-canary.201
This release includes updates related to custom cache handlers, React versions, decoding of encrypted closures, props types modification, tag manifest handling, and test improvements.
Relevance to Netlify:
The changes related to custom cache handlers, React updates, decoding, and tags manifest handling could impact the Netlify Next.js Runtime and build process. Improvements in e2e tests and TypeScript code blocks in documentation contribute to better testing and documentation practices for Netlify.
v15.0.0-canary.200
The release includes improvements related to dynamicIO, build warnings, tag staleness checking, codemod, and access warnings for Request APIs. Misc changes involve transforming and allowing 'use cache' functions in certain contexts.
Relevance to Netlify:
The changes related to dynamicIO, build warnings, and API access warnings could impact the Netlify Next.js Runtime by potentially affecting middleware handling or build processes. The codemod feature might require updates to Netlify's build or deployment processes. The 'use cache' functions updates could be relevant to Netlify's edge functions or documentation.
v15.0.0-canary.199
The release includes improvements related to cache handling, static path generation, and error messages. There are also updates to edge log tests and documentation.
Relevance to Netlify:
The focus on cache handlers, static path generation, and error message differentiation can impact the Netlify Next.js Runtime in terms of optimizing caching strategies and handling server-side rendering. Updates to edge log tests can potentially affect Netlify's build process or edge functions. Documentation changes may require updates to Netlify's documentation.
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.