Tom Lienard

This commit **fixes a critical bug** in the **`vercel-sandbox` package** that caused unhandled promise rejections during log fetching, potentially crashing the Node.js process. It **refactors the log streaming logic** within `_runCommand` into a new `pipeLogs` function, adding explicit error handling to catch failures when `getLogs` returns a non-ok status. This **improves the stability and reliability** of command execution by preventing application crashes related to log errors, and new tests in `sandbox.test.ts` verify the correct error handling.

This commit **fixes a bug** in the **`sandbox` package's `cp` command** that previously required local destination files to exist before a copy operation could succeed. It **refactors the path parsing logic** within `packages/sandbox/src/commands/cp.ts` to allow `fs.writeFile()` to create the target file if it's not present, while still validating the source. This **improves the usability** of the `cp` command by making it more flexible, and also includes **enhanced error messages, updated logging**, and **new tests** for the `parseLocalOrRemotePath` utility.

This commit adds a changeset file, preparing for a **patch release** that addresses **400 errors** encountered during **sandbox interactions**. This **maintenance** task ensures the proper publication of the `@vercel/sandbox` package, allowing the `sandbox` CLI to correctly integrate a critical revert. The fix targets the core **sandbox interaction functionality**, resolving reliability issues for users of both the **`sandbox` CLI** and the **`@vercel/sandbox` SDK**.

This commit **fixes 400 errors** encountered during various **sandbox interactions** within the `vercel-sandbox` package. The issue stemmed from the **incorrect propagation of `privateParams`** (specifically `__includeSystemRoutes`) to sandbox API methods that do not support them, a regression introduced by a previous change. To resolve this, the commit **removes the erroneous `privateParams` handling** from the `api-client` methods and the `Command` and `Sandbox` classes. This ensures correct parameter management across operations such as `runCommand`, `writeFiles`, and `stopSandbox`, significantly improving the **stability and reliability of the sandbox environment**.

This commit introduces a **new capability** to the **Sandbox SDK** and **CLI**, enabling users to specify custom or infinite expiration times for snapshots. The `sandbox.snapshot()` method and the `snapshot` CLI command now accept an `expiration` parameter, which can be set to a duration in milliseconds or `0` for a never-expiring snapshot, overriding the previous default 7-day expiration. This **feature enhancement** provides greater flexibility in managing snapshot lifecycles, allowing for permanent snapshots or precise control over their duration. The change involves updates to the API client, snapshot schema, and related utility functions to support this new expiration logic.

This commit delivers a **bug fix** addressing incorrect column widths in the **CLI's table output**. Previously, tables would render with misaligned columns due to an inaccurate calculation of string lengths, particularly when VT control characters were present. The fix, implemented in `packages/sandbox/src/util/output.ts`, now correctly strips these control characters when determining visible string length, ensuring proper column alignment and padding. This significantly improves the readability and presentation of all **CLI tables** for users.

This commit introduces a **new `aborted` status** for sandboxes, enhancing both the **`sandbox` CLI** and the **`vercel-sandbox` API client**. It updates the `list` command within the `sandbox` CLI to correctly display sandboxes that are in an `aborted` state, alongside `snapshotting`, with appropriate visual indicators. Concurrently, the `Sandbox` Zod schema in the API client is extended to officially recognize `aborted` as a valid status and include an optional `abortedAt` timestamp field. This **new capability** improves the accuracy of sandbox state reporting and ensures robust data validation across the system.

This commit provides a crucial **documentation update** across the project's READMEs to ensure accuracy and improve user experience. It **revises the root `README.md`** by updating the **getting started guide** with **revised setup commands** and a **new example demonstrating the Sandbox SDK**, thereby enhancing the **onboarding experience** for new users. Concurrently, the `packages/vercel-sandbox/README.md` is updated to reflect the **significant scale** of the underlying infrastructure, now powering over 2 million builds daily. This **maintenance work** ensures all documentation is current and provides comprehensive guidance for project setup and understanding the system's impact.

This commit performs **maintenance** and **documentation updates** across several project packages. It standardizes `package.json` metadata for the **`pty-tunnel-server`**, **`pty-tunnel`**, **`sandbox`**, and **`vercel-sandbox`** packages, primarily by updating the license field to Apache-2.0 and adding or correcting `homepage`, `repository`, `description`, and `keywords`. Concurrently, the `README.md` files for the **`sandbox`** and **`vercel-sandbox`** packages are significantly improved, offering clearer descriptions, login instructions, and streamlined 'Getting started' guides. This work enhances project consistency and improves the initial user experience for these tools.

This commit **updates several documentation links** across the project to prevent breakage with upcoming documentation page changes. It primarily affects the **example README files**, where links related to **personal access tokens** are corrected. Additionally, internal documentation links within the `packages/sandbox` and `packages/vercel-sandbox` modules, specifically for **authentication** within the `token` command option and **sandbox usage** in error messages, have been updated. This **maintenance chore** ensures users are directed to the correct and current documentation, improving the overall user experience and preventing confusion.

This commit introduces a **new feature** to the **Vercel Sandbox SDK**, specifically enhancing the **`Snapshot` class** by adding new getter methods. It now exposes `sizeBytes`, `createdAt`, and `expiresAt`, allowing consumers to programmatically retrieve detailed metadata about a snapshot. This change provides greater visibility and control over snapshot properties, enabling more comprehensive management and inspection of snapshot objects within the SDK.

This commit introduces significant **CLI command restructuring** within the **`sandbox` module**, primarily by **renaming and aliasing commands** for improved clarity and consistency. The `sandbox ssh` command has been renamed to `sandbox connect`, with `ssh` and `shell` provided as backward-compatible aliases. Furthermore, the `sandbox sh` command is now deprecated and automatically remapped to `sandbox create --connect`, which is a new flag added to the `create` command to allow immediate connection after sandbox creation. This **refactoring** enhances the user experience by streamlining command names while ensuring a smooth transition for existing users through intelligent remapping and warnings.

This commit **adds a missing changeset entry** to document the recently introduced **support for network policies**. This **maintenance chore** rectifies an oversight from previous pull requests that introduced new features without corresponding release notes. The addition of this changeset is essential to **trigger a new release of the SDK/CLI**, ensuring that the network policy capabilities are properly announced and made available to users.

This commit introduces comprehensive **snapshot management capabilities** to the `sandbox` CLI, enabling users to create, list, delete, and restore sandboxes from saved states. It integrates new commands like `sandbox snapshot` to create snapshots, `sandbox snapshots list` and `sandbox snapshots delete` for managing them, and extends `sandbox create` to provision new sandboxes from a specified snapshot ID. This significant **new feature** enhances the **`sandbox` module** by providing persistence and reproducibility for sandbox environments, impacting the core CLI application and its client-side interactions. Utility functions for output formatting were also refactored to support these new commands.

This commit **introduces a new example** within the **`examples`** directory, specifically demonstrating the usage of **filesystem snapshots**. It provides a **new capability example** through `filesystem-snapshots.ts`, illustrating how to create, list, and interact with these snapshots. This addition serves as a practical guide for developers to understand and implement filesystem snapshot functionality, particularly relevant for platforms like Vercel Sandboxes. The example includes its own `README.md` for detailed instructions and is referenced in the main `examples/README.md`.

This commit **enhances** the **lambda bundling logic** by dynamically adjusting the maximum uncompressed function size threshold based on the runtime. It **reduces the effective limit for the Bun runtime** from 250 MiB to 150 MiB, accounting for Bun's inherent binary size and preventing potential bundling issues. This is achieved by introducing a new `getMaxUncompressedLambdaSize` utility function in `packages/next/src/utils.ts`, which replaces the static `MAX_UNCOMPRESSED_LAMBDA_SIZE` constant. The `getPageLambdaGroups` and `detectLambdaLimitExceeding` functions in `packages/next/src/server-build.ts` now utilize this dynamic limit, ensuring more aggressive function splitting and accurate warnings for **Bun runtime** users.

This commit introduces support for the new `/_vercel/ping` endpoint within the **Python runtime**, specifically modifying the `do_POST` function in `vc_init.py`. This **new capability** is a foundational step to replace the existing `handler-started` IPC message, improving how the Vercel platform monitors the readiness of Python functions. While initially a no-op, this change enables future updates in the Vercel runtime to utilize this more robust ping mechanism. It represents a **precursor to a larger refactoring** aimed at enhancing the stability and efficiency of Python function deployments.

This commit introduces a **new capability** allowing users to configure the `architecture` (`x86_64` or `arm64`) for **Vercel Serverless Functions** directly within their `vercel.json` file. Previously only available via the Build Output API, this feature now integrates `architecture` into the `functions` configuration schema, affecting **build utilities**, **Next.js**, and **Node.js builders**. The change updates type definitions, schema validation, and builder logic to support this new option. This enables developers to specify the desired CPU architecture per function, offering greater control and potential performance or cost optimizations for their deployments.

This commit **refactors** the **`@vercel/python` package** by **removing the deprecated `VERCEL_IPC_FD` environment variable usage**. The Python runtime's Inter-Process Communication (IPC) setup is now simplified to exclusively use `VERCEL_IPC_PATH`, as the migration to this newer mechanism is complete. This **maintenance** task cleans up legacy code within `vc_init.py`, ensuring a more consistent and streamlined internal communication process for Python deployments. The change also includes documentation of this removal in a new changeset file.

This commit **enhances the `@vercel/python` runtime's build output** by adding a new flag, `supportsResponseStreaming: true`. This **compatibility enhancement** ensures that **response streaming capabilities** are only applied to Python functions when the runtime explicitly indicates support. It addresses potential issues with older Vercel CLI versions or build caches, preventing the incorrect application of streaming. This change is crucial for the **Python runtime** to safely and reliably roll out its streaming functionality.