Felix Haus

This commit introduces **`--archive` flag support** to the **`vercel deploy continue` command**, aligning its functionality with the standard `deploy` command. It **enhances the `@vercel/client` package** by refactoring tarball creation into a shared `createTgzFiles` utility, which is now utilized by both `createDeployment` and `continueDeployment`. A key aspect of this **new capability** is the special handling of `provision.json`, which is now excluded from the tarball and sent as a standalone file when `--archive=tgz` is used, ensuring the API can inspect it pre-build. This **feature addition and refactoring** improves deployment efficiency and consistency across CLI commands, with comprehensive unit tests added to cover the new behavior.

This commit introduces a **bug fix** and **enhancement** to the **Vercel CLI's `deploy` command**, specifically when using the `--json` flag. Previously, failed deployments (due to build errors, cancellations, or failed checks) would not output JSON, hindering automation. Now, the **CLI** consistently outputs a JSON object containing deployment information and an `error` field for all deployment outcomes, including failures. This change significantly improves the **scriptability and reliability** of automated workflows that parse `vercel deploy` output, ensuring a predictable JSON response for all scenarios.

This commit introduces a **new capability** to the **`@vercel/cli`** by adding `--json` and `--format=json` flags to the `vc deploy init` command. This enhancement allows the command to output critical deployment details, such as `id` and `url`, in a **machine-readable JSON format** to stdout, significantly improving its utility for **automation scripts**. The change also includes telemetry tracking for flag usage, suppresses the bare URL output when JSON is requested to prevent malformed output, and is thoroughly covered by new unit tests. This **feature** streamlines programmatic interaction with the deployment initialization process, making it easier to integrate into CI/CD pipelines.

This commit introduces a **memory efficiency improvement** within the **`build-utils` package**, specifically in the `FileBlob.fromStream()` method. It **refactors** the stream collection logic to avoid unnecessary `Buffer` copies by checking if incoming chunks are already buffers before processing. This **optimization** significantly **reduces peak memory usage** from approximately 3x to 2x the file size when handling large streams, preventing redundant data duplication and improving overall resource management.

This commit introduces significant **performance optimizations** and **refactoring** to the **`build-utils` package**'s Node.js version detection logic. The `isNodeVersionAvailable` function now uses `statSync({ throwIfNoEntry: false })` for more efficient filesystem checks, replacing a less performant try-catch pattern. Crucially, `getAvailableNodeVersions` is optimized to **skip filesystem checks for Node.js versions older than 18**, as these are discontinued and not present in the build container, thereby reducing unnecessary I/O operations. This **maintenance** work also updates an error message to explicitly mention "discontinued" versions, providing clearer guidance to users requesting unsupported Node.js runtimes and resulting in **faster Node.js version resolution** within the build process.

This commit performs a **monorepo-wide dependency upgrade** by updating `@types/node` to `20.11.0` across all relevant packages. It introduces the `syncpack` tool to **enforce consistent versioning** for this critical dependency, adding a new **CI check** to prevent future discrepancies in the `.github/workflows/test-lint.yml` workflow. This **maintenance** effort addresses compatibility issues with the project's TypeScript 4.9.5, which cannot parse newer `@types/node` versions, and includes **type compatibility fixes** in modules such as `@vercel/cervel`, `@vercel/cli`, and `@vercel/go`. The overall impact is a more stable and consistent development environment for Node.js-related code by standardizing type definitions.

This commit introduces a **performance optimization** within the **`build-utils` package** by refactoring how `package.json` files are located. Previously, the `getNodeVersion` utility unnecessarily scanned for and parsed multiple lockfiles when it only required `package.json` information. A new, lightweight `findPackageJson` utility has been added to specifically locate `package.json` without lockfile scanning, and `getNodeVersion` now utilizes this function. This **refactoring** significantly **improves performance** by reducing file system I/O and parsing overhead for operations dependent on `getNodeVersion`.

This commit **enhances the Go builder** by explicitly setting the `runtimeLanguage` property to `'go'` when creating Lambda functions. This ensures that **Go-based serverless functions** are correctly identified within the Vercel platform. It represents a **new capability** for the Go runtime, improving metadata accuracy and enabling proper classification. This change is dependent on a prior update to `@vercel/build-utils` to support `'go'` as a valid runtime language, crucial for the **proper classification and handling of Go-based serverless functions**.

This commit **introduces support for 'go' as a valid runtime language option** within the **`@vercel/build-utils` package**. It **extends the `LambdaExecutableRuntimeLanguages` type** and updates the `Lambda` constructor's validation logic in `src/lambda.ts` to correctly accept `'go'`, mirroring the existing support for `'rust'`. This **new capability** is a foundational step towards enabling Go-based serverless functions on Vercel, ensuring the build system can validate this new runtime. The actual Go builder integration will be implemented in a subsequent release, building upon this core validation change.

This commit **disables automatic Sentry session tracking** within the **CLI module**. By setting `autoSessionTracking` to `false` during Sentry initialization in `packages/cli/src/index.ts`, this **configuration change** prevents the CLI from automatically sending session-related data. This **maintenance task** reduces data collection overhead and enhances user privacy for CLI interactions.

This commit **expands the CI test matrix** to include **Node.js 24.x**, ensuring the project's compatibility with the latest runtime. It updates the `.github/workflows/test.yml` configuration to run tests against `node24` and upgrades the `@datadog/datadog-ci` uploader to version `4.2.2`. To address an `npm` issue on Windows with Node.js 24, the workflow now uses `pnpm dlx` instead of `npx`. Furthermore, `utils/chunk-tests.js` is updated to support Node.js 24 and utilize the `node:` prefix for built-in module imports. This **maintenance** work significantly enhances the project's **CI/CD pipeline** and test coverage.

This commit **enables default support for Node.js 24.x** within the build system, specifically impacting the **`build-utils`** package. It **removes the temporary environment variable check** that previously issued a warning when running local builds with Node.js 24.x, effectively making Node.js 24.x a fully supported version. This **feature enablement** improves the developer experience by allowing users to seamlessly use Node.js 24.x without encountering deprecation warnings. Extensive **unit and integration tests** across the `build-utils`, `cli`, and `node` packages were updated to reflect this new default support and ensure correct behavior.

This commit performs **maintenance** within the **`build-utils`** package by **removing the deprecated `--unsafe-perm` flag** from `npm install` commands. Specifically, the `getInstallCommandForPackageManager` function in `packages/build-utils/src/fs/run-user-scripts.ts` no longer includes this flag, which was causing **deprecation warnings** with `npm` v11 (bundled with Node.js 24). This **refactoring** ensures cleaner build logs and prevents potential breakage in future `npm` versions, as the flag has been irrelevant since `npm` v7. The change improves the **reliability of the build process** by aligning with modern `npm` behavior.

This commit introduces **experimental support for Node.js v24** within the **`build-utils`** package, allowing it to be recognized and used when a specific environment variable is set. It implements new logic in `packages/build-utils/src/fs/node-version.ts` to conditionally enable this latest Node.js runtime, mirroring the approach taken for previous major versions. This **new capability** empowers developers to opt-in and test their projects with Node.js v24, enhancing the platform's compatibility with cutting-edge environments. Comprehensive unit tests have been added to validate the correct behavior of this conditional version allowance.