Steven

This commit **improves documentation** by adding a direct link to the **Turborepo Docker guide** within the `prune --docker` flag section of the reference documentation. Specifically, the `apps/docs/content/docs/reference/prune.mdx` file is updated to include this link. This **documentation enhancement** ensures that users reading about the Docker-optimized output format can easily navigate to the guide containing an example Dockerfile. The change streamlines the **user experience** by providing immediate access to practical examples for integrating `prune` with Docker.

This commit performs a **dependency update** for the **`go` package**, specifically bumping the `tar` development dependency from version `7.5.7` to `7.5.11`. This **maintenance chore** ensures that the project utilizes the latest stable and potentially more secure version of the `tar` utility during development and build processes. The change primarily impacts the **development environment** for the `go` module, with no direct effect on runtime functionality or user-facing features.

This commit **updates the documentation** for the **Image component** to clarify the interaction between `images.remotePatterns` and `images.maximumRedirects`. It explains that `remotePatterns` applies to the initial URL, while redirects are followed up to the `maximumRedirects` limit, with the final response always needing to be an image. This **documentation enhancement** addresses common user confusion regarding image loading behavior and redirect handling, ultimately improving developer understanding and preventing potential misconfigurations.

This commit **reverts** the URL encoding of cache tags within the **`@vercel/functions` package**, specifically impacting the **Vercel Runtime Cache**'s tag handling. This **regression fix** undoes a previous change that caused issues when using special characters like colons in cache tags. By removing `encodeURIComponent` from methods like `set()` and `expireTag()` in `packages/functions/src/cache/index.ts`, the system now correctly interprets commas as delimiters for multiple tags, restoring the expected behavior for **cache invalidation**. This ensures that tags with special characters are passed through unencoded, preventing unintended side effects and improving the reliability of cache operations. Associated tests in `packages/functions/test/unit/cache/index.test.ts` have also been updated to reflect this change.

This commit introduces a **new capability** by implementing an **LRU disk cache** for the **Next.js Image Optimization API**, significantly improving performance and disk space management. It adds a new configuration option, `images.maximumDiskCacheSize`, allowing users to define the maximum disk space allocated for optimized images, with a default of 50% of available disk space if not specified. This **feature** ensures that least recently used entries are automatically evicted, while frequently accessed images remain cached and are promoted upon access. The change involves extensive additions to the `ImageOptimizerCache` logic, a new `disk-lru-cache` module, updated `image.mdx` **documentation**, and comprehensive **integration tests** to validate eviction and size limits. This ensures efficient resource utilization and better responsiveness for image serving, with existing cache entries replayed on `next start` to respect new size limits.

This commit introduces a **new capability** to the **`build-utils`** package by adding an optional `exposeErrBody` boolean property to the **`Prerender`** object. This property allows developers to explicitly control whether error bodies are exposed during the prerendering process, providing more granular configuration over error handling. The change includes **validation** for the new property within the `Prerender` constructor and is accompanied by **unit tests** to ensure its correct behavior. This enhancement offers greater flexibility in managing prerendering error output and its visibility.

This commit **enhances the Vercel CLI's user experience** by **updating the help text** for the `vc blob` command. Specifically, the description for the `store` subcommand in `packages/cli/src/commands/blob/command.ts` is changed to "Manage or create a Blob store". This **documentation improvement** aims to **increase the discoverability** of the `vc blob store add` command, making its purpose clearer to users.

This commit **optimizes memory usage** within the **Next.js Image component** by significantly reducing the default `maximumResponseBody` for its image optimization loader from 300MB to 50MB. This **performance optimization** is a **configuration adjustment** based on metrics showing that the vast majority of source images are well within the new 50MB limit, aiming to **reduce memory consumption** during image processing. The change primarily affects the `packages/next/src/shared/lib/image-config.ts` module, with corresponding updates to the `docs/01-app/03-api-reference/02-components/image.mdx` documentation and various integration and unit tests to reflect the new default. This adjustment will lead to more efficient resource utilization for most applications, though users with exceptionally large source images may need to explicitly configure a higher limit.

This commit **upgrades the `sharp` image processing library to version `0.34.5`**, primarily affecting the **`next/image` component** and its associated integration tests by updating the `sharp` dependency in `packages/next/package.json` and `test/integration/sharp-api/app/package.json`. This **dependency update** incorporates critical **bug fixes** from `libvips v8.17.3`, enhances error messaging, and adds new capabilities such as experimental support for Linux RISC-V 64-bit binaries and BigTIFF output. The upgrade ensures that image optimization within Next.js benefits from the latest stability improvements and expanded feature set of the underlying image processing engine.

This commit introduces the **`images.maximumResponseBody` configuration option** to the **Next.js Image component**, enabling control over the size of external images processed during optimization. It allows the **image optimizer** to **exit early** from `fetchExternalImage` if an image's response body exceeds the configured limit, thereby preventing resource exhaustion when handling overly large source images. This **new capability** significantly enhances the **robustness and performance** of the image optimization pipeline by mitigating potential issues from large or malformed image responses. The change includes updates to the configuration schema, default values, and comprehensive **documentation and tests**.

This commit introduces a **bug fix** for the **Next.js Image component**, specifically addressing an edge case where the `?dpl` query parameter was erroneously appended to image `src` URLs. Previously, when `unoptimized=true` and the `src` was an absolute URL missing a protocol (e.g., `//example.com/image.png`), the `?dpl` parameter would still be added, potentially leading to incorrect image requests. The `generateImgAttrs` function in `packages/next/src/shared/lib/get-img-props.ts` has been updated to prevent this, ensuring that **unoptimized images** with protocol-relative URLs are correctly processed. A new **unit test** has been added to `test/unit/next-image-get-img-props.test.ts` to validate this corrected behavior.

This commit introduces a **bug fix** for the **`next/image` component**, ensuring **consistent deployment tracking** for local images. Previously, the `?dpl` query parameter was only added to statically imported local images, but this change extends its application to *all* local image `src` values that start with `/`. This **resolves issues for microfrontends** with path prefixes that were failing skew protection, by modifying the `defaultLoader` in `image-loader.ts` and the `generateImgAttrs` function in `get-img-props.ts`. The update improves the reliability of image loading and deployment-specific caching for local assets across the application.

This commit **updates documentation links** for the **`@vercel/functions` package** to ensure users are directed to the correct resources. It **corrects an outdated README link** in `packages/functions/README.md` that was previously causing redirects, now pointing directly to the current API reference page. Additionally, the `homepage` URL in `packages/functions/package.json` is updated to reflect this new documentation, improving discoverability for users accessing the package via npm. This is a **documentation maintenance fix** that enhances user experience by providing accurate and accessible information.

This commit introduces **new cache management capabilities** to the **`@vercel/functions` package** by implementing and exposing `invalidateBySrcImage` and `dangerouslyDeleteBySrcImage`. These **new APIs** allow developers to programmatically **invalidate or delete cached items specifically by their source image URL**, enhancing control over cached image assets. The `PurgeApi` interface has been extended with these methods, and relevant documentation has been updated to reflect their availability. This **feature enhancement** provides more granular cache control, enabling more efficient and precise cache purging strategies for image-dependent applications.

This commit introduces a **new capability** to the **Vercel CLI** by adding the `--srcimg` option to the `vercel cache invalidate` and `vercel cache dangerously-delete` commands. This enhancement allows users to **semantically invalidate or delete cache entries specifically tied to a source image path**, such as `/api/avatar/1`. The change impacts the **CLI's cache management subsystem**, providing more granular control over cached assets and improving the developer experience for managing image-related cache. Telemetry tracking for this new option has also been integrated, alongside comprehensive unit tests to ensure functionality.

This commit **refactors** the **Next.js image optimization** feature by replacing the `is-local-address` dependency with `ipaddr.js` for more robust private IP address detection. A new `isPrivateIp` utility function, powered by `ipaddr.js`, is introduced and integrated into the `fetchExternalImage` logic within the **image optimizer**. This **dependency swap** and associated **code refactoring** enhance the reliability and security of external image fetching by ensuring more accurate private IP validation. The change also includes **new tests** for the `isPrivateIp` utility and updates to **build configurations** and **NFT tests** to reflect the new dependency.

This commit introduces **new configuration options** for the **Next.js image optimization system**, `images.dangerouslyAllowLocalIP` and `images.maximumRedirects`. The `dangerouslyAllowLocalIP` option, defaulting to `false`, controls whether images from local IP addresses can be optimized, primarily for self-hosted private networks. Concurrently, `images.maximumRedirects` now defaults to 3, limiting the number of HTTP redirects followed during image fetching. This is a **breaking change** for users who previously relied on local IP image optimization or required more than three redirects, necessitating explicit configuration adjustments in `next.config.js`. The changes impact the core image optimization logic in `packages/next/src/server/image-optimizer.ts` and are reflected in the configuration schema and documentation.

This commit **removes the 16px image size from the default `images.imageSizes` configuration** within **Next.js**, impacting the **`next/image` component** and the **Image Optimization API**. This **breaking change** is a **performance optimization** based on telemetry data showing minimal usage of the 16px size, aiming to **reduce `srcset` complexity** and the number of image variations generated by the backend. While most applications will benefit from a leaner default configuration, projects explicitly requiring 16px images will now default to 32px unless they **reconfigure `images.imageSizes`** to include 16px. The change affects core configuration, documentation, and various integration and unit tests.

This commit **deprecates** the `next/legacy/image` component, which was initially provided as a migration path from Next.js 12 to 13. A **runtime warning** is now emitted the first time `next/legacy/image` is used, indicating its planned removal in a future Next.js version. This **maintenance feature** primarily impacts the **Next.js Image component (legacy)** and its **documentation**, encouraging developers to transition to the modern `next/image`. Associated integration tests have been updated to verify the presence or absence of this new deprecation warning.

This commit **enforces the deprecation** of the `images.domains` configuration within the **Next.js Image component**, introducing a **warning mechanism** to alert users in Next.js 16 when this setting is still in use. It updates the **server-side configuration processing** (`config.ts`) to emit these warnings and marks the property as deprecated in `image-config.ts`. The change aims to guide developers towards using the more secure `images.remotePatterns` for image optimization, thereby enhancing the **security and maintainability** of applications. New tests ensure the warning is correctly displayed in both development and production environments.