Deployments now show build cache size

Deployment summaries now include the size of the build cache each deployment saved and how close it is to the limit for its build machine. This information is also available in the CLI using vercel inspect version 65.1.0 or newer, as well as through the get-deployment REST API endpoint. The feature aims to provide transparency about cache usage and storage constraints.

The build cache size is billable as part of build time, and caches exceeding the limit are discarded before the next build starts. This ensures users are aware of storage costs and potential impacts on subsequent deployments. The feature is enabled by default for all deployments built on or after October 21.

Users can now monitor their build cache usage directly within deployment summaries, CLI, and API responses. This helps teams avoid unexpected cache discards and optimize storage costs. The feature applies to all build machines and plans, providing consistent visibility across environments.

The maximum build cache size varies depending on the build machine type, with details available in the official documentation. This allows users to plan their storage needs accordingly and adjust their build strategies to stay within limits.