Luke PS

This commit introduces a **new capability** to the **`vercel-sandbox`** package, allowing users to specify file permissions (`mode`) directly when calling the `writeFiles` API. The `Sandbox.writeFiles`, `APIClient.writeFiles`, and `FileWriter.addFile` methods have been updated to accept an optional `mode` property, which is then passed to the underlying `tar-stream` for setting permissions. This enhancement **streamlines file creation** by eliminating the need for a separate `chmod` command after writing files, particularly useful for executables. This **feature** improves the efficiency of sandbox interactions by reducing the number of required operations and includes updated JSDoc for clarity.

This commit introduces a **refactoring** effort to rename the import alias for the `fetch` function, specifically when it originates from the `node-fetch` library, to `nodeFetch`. This change primarily affects **test files** and fixtures across various packages, including `packages/cli`, `packages/frameworks`, `packages/next`, `packages/node`, and `packages/python`. The goal is to improve code clarity and prevent naming conflicts with the native `fetch` API within the **testing infrastructure**. This is a **low-risk maintenance** task that ensures no changes to production code logic or behavior, and it is documented with a new changeset entry.

This commit performs a **pure refactoring** by renaming the imported `fetch` identifier to `nodeFetch` wherever the `node-fetch` library is used across the codebase. This change primarily affects various **CLI utilities**, **API examples**, and **build-related packages** such as `build-utils`, `go`, and `static-build`, along with their corresponding test files. The purpose is to improve code clarity, prevent potential naming conflicts, and prepare for future migrations to the native `fetch` API. As a **low-risk change**, this **refactoring** introduces **no functional impact** or alteration to existing behavior.

This commit **upgrades** the project's core development tools by updating the `turbo` dependency from version 2.5.3 to 2.8.10 and the `pnpm` package manager to its latest version. This **maintenance chore** ensures the project benefits from the newest features, performance improvements, and bug fixes provided by these critical build and package management systems. The changes primarily affect the **developer workflow** and **CI/CD pipelines**, potentially leading to more efficient builds and reliable dependency management across the project.

This commit performs a **refactoring** within the **`packages/client`** module by **renaming** the internal `fetch` utility function to `fetchApi`. This change clarifies the distinction between the project's custom API fetching utility and the native browser `fetch` API, addressing potential naming confusion and preparing for future migrations. All internal call sites across features like **deployment status checks, deployment initiation, continuation, and file uploads** have been updated to use the new `fetchApi` name. This **maintenance** effort also includes updating relevant test mocks and is a low-risk change with no functional impact, primarily preparing the codebase for easier future integrations involving the underlying `fetch` mechanism.

This commit performs a **documentation update** by revising the daily build count stated in the project's `README.md` file. The figure has been updated from 1 million to 2 million, reflecting the **increased scale and activity** of the project's build processes. This **maintenance change** ensures that the public-facing documentation accurately represents the current operational metrics.

This commit **reverts** a previous change that renamed the `getRuntimeNodeVersion` function to `getNodeVersion` across the codebase. This **maintenance revert** primarily impacts the **`build-utils`** package and various **framework builders** (e.g., `next`, `node`, `remix`, `gatsby`, `redwood`, `static-build`) that had adopted the new function name. The reversion is a **critical stability measure** to prevent potential **breaking changes for external builders** and ensure the integrity of the CLI for an upcoming release. It temporarily restores the original function name while further usage analysis is conducted.

This commit performs a significant **refactoring** across multiple **builder packages** (e.g., `@vercel/next`, `@vercel/node`, `@vercel/remix`, `@vercel/hydrogen`, `@vercel/redwood`, `@vercel/static-build`) and core **backends** to remove the direct usage of `getSpawnOptions` and `getRuntimeNodeVersion`. This **maintenance** effort adapts the build process to leverage the Vercel environment's new capability of populating necessary toolchains, centralizing environment variable management through `spawnEnv`. The change simplifies builder logic by eliminating the need for builders to provision toolchains or re-create `$PATH`, ensuring a more streamlined and consistent execution environment for user-space subprocesses. Consequently, the `getSpawnOptions` function in `build-utils/src/fs/run-user-scripts.ts` is now deprecated.

This commit **refactors** the internal utility for determining the Node.js version by **renaming `getNodeVersion` to `getRuntimeNodeVersion`**. This change clarifies that the function now retrieves the **runtime Node.js version** by executing `node --version`, leveraging the Vercel environment's `$PATH` provisioning instead of reading files from disk. The update impacts various **framework builders** across `packages/build-utils`, `packages/backends`, `packages/gatsby-plugin-vercel-builder`, `packages/hydrogen`, `packages/next`, `packages/node`, `packages/redwood`, `packages/remix`, and `packages/static-build`, streamlining how they identify the active Node.js environment. This **maintenance** improvement enhances efficiency and sets the stage for future optimizations by reducing unnecessary file system operations.

This commit introduces **early validation** and **enhanced error messages** for the **Next.js build output directory** within the `packages/next` module. It adds checks to ensure the output directory exists and is not empty, preventing generic `routes-manifest.json` errors that previously obscured issues like misconfigured `outputDirectory` or incorrect Turborepo caching. This **developer experience improvement** provides specific error codes (`NEXT_OUTPUT_DIR_MISSING`, `NEXT_OUTPUT_DIR_EMPTY`) and actionable guidance, making it easier for users to diagnose and resolve Next.js build failures. The **documentation** for these errors has also been updated to reflect the new, more detailed explanations.

This commit performs a significant **refactoring** of the **build environment setup** by **removing the `getSpawnOptions` utility function** from the CLI. This function, previously responsible for configuring subprocesses with the correct Node.js `PATH`, is now redundant as its logic has been ported to the Vercel build platform. Consequently, various **framework builders** such as **Next.js, Node.js, Hydrogen, Redwood, Remix, and Static Build** have been updated to directly use `getEnvForPackageManager` for environment variable handling. This change **decouples the CLI** from platform-specific environment logic, making it a smaller wrapper and shifting responsibility for zero-config environment detection to the build container.

This commit introduces a **new capability** to the **client-side deployment process**, enabling it to explicitly signal when a deployment is prebuilt. It modifies the `packages/client/src/utils/query-string.ts` utility to conditionally add a `prebuilt=1` query string argument to the deployment creation endpoint, specifically via the `generateQueryString` function. This crucial change informs the **API Deployments service** that the full user build flow can be bypassed, significantly **optimizing the deployment of prebuilt artifacts**. The work streamlines the interaction between the client and the deployment API, improving efficiency for pre-compiled projects.

This commit **updates the Vercel approvers configuration** by modifying the role of the `@vercel/ci-cd` team within the `.vercel.approvers` file. The team's role is changed from 'notify' to 'team', enabling them for optional approvals in the deployment process. This **configuration update** is a **maintenance chore** that directly impacts the **CI/CD workflow** and **deployment approval process**, ensuring the specified team is properly integrated into the optional approval structure.

This commit **initializes the CODEOWNERS system** for **Vercel deployments** by introducing a new `.vercel.approvers` configuration file at the project's root. This **infrastructure setup** designates `@vercel/ci-cd` for optional notifications, ensuring relevant teams are aware of changes impacting the Vercel environment. The addition of this top-level CODEOWNERS file establishes a foundational mechanism for managing code ownership and review processes within the **CI/CD pipeline** for Vercel-specific modifications.

This commit introduces **`vlt` support** to the **`build-utils`** package, enabling automatic detection and management of this package manager. It's a **new capability** that extends the zero-config package manager detection logic within `src/fs/run-user-scripts.ts`. Specifically, the system can now identify `vlt` lockfiles via `validLockfileForPackageManager`, generate appropriate installation commands using `getInstallCommandForPackageManager`, and execute user scripts using `vlt` through `runPackageJsonScript`. This enhancement allows projects utilizing `vlt` to seamlessly integrate with the build process, improving compatibility and user experience for a broader range of development setups.

This commit introduces a **new feature** within the **`build-utils` package** to ensure that **AWS Lambda functions** always have their architecture explicitly defined. It adds a new utility, `getDefaultLambdaArchitecture`, to **automatically determine the default Lambda architecture** based on the process architecture during function creation. This **enhancement** guarantees that the `Lambda` class consistently initializes with a specified architecture, improving the reliability and predictability of Lambda deployments by preventing ambiguous or unset architecture configurations.

This commit introduces a **critical fix** and **refactoring** to enhance **ESM module detection** within the **Remix build process**, specifically for packages using `"type": "module"`. It **refactors** the `isESM` utility in `packages/remix/src/utils.ts` to asynchronously determine ESM status based on file extension, `package.json` type, and Node.js version, while also correcting its asynchronous usage in `packages/remix/src/build-legacy.ts`. This ensures **Remix v2 correctly supports ESM modules** on **Node.js 20 and newer**, resolving previous compatibility issues. The change is validated by re-enabling relevant integration tests.

This commit implements a **reliability improvement** for the project's **observability infrastructure**, specifically concerning **tracing during build processes**. It ensures that **root spans** associated with build commands are always properly **finished and flushed**, even when the build step encounters an error. This prevents the loss of critical trace data, providing more complete and accurate insights into build performance and failures. The change guarantees that **trace data** for build operations is consistently available for debugging and analysis, enhancing the overall reliability of monitoring.

This commit **enhances the diagnostics collection** within the **Next.js build process** by including the `.next/turbopack` marker file in the `diagnostics` glob. This **new feature** allows the **Vercel build pipeline** to detect when a project has been built using **Turbopack**. By collecting this specific file, the system can then provide users with clear indications that their build leveraged Turbopack, improving transparency and user feedback regarding the build environment.

This commit **standardizes the detection path for `pnpm@6`** within the **Vercel build system**, updating the `detectPackageManager` function in `packages/build-utils/src/fs/run-user-scripts.ts` to use a consistent `/pnpm6/node_modules/.bin` location. This **infrastructure improvement** ensures the build system can automatically locate and utilize `pnpm@6` from a standardized path, facilitating seamless user migrations. The change allows for arbitrary upgrades of default `pnpm` versions without requiring modifications to zero-config build configurations, significantly enhancing the **flexibility and maintainability** of the build process for `pnpm` users.