Austin Merrick

This commit delivers a **bug fix** for the **CLI**'s **rate limiting message display**, specifically addressing an issue where incorrect retry times were shown. Previously, when a deployment flood rate limit was exceeded, the CLI would display an astronomically large and inaccurate retry duration because the `error.limit.reset` value, which is in epoch milliseconds, was erroneously multiplied by 1000. The fix corrects the calculation within `packages/cli/src/util/index.ts` by removing this incorrect multiplication, ensuring that users now receive accurate and sensible retry instructions. This improves the user experience by providing correct feedback during rate limit encounters.

This commit **reverts a previous feature** in the **Vercel CLI** that introduced an automatic promotion flow when setting an alias for a production deployment. Specifically, it **removes the logic** within `packages/cli/src/commands/alias/set.ts` that utilized `isProductionAlias` and `tryPromoteForProductionAlias` to trigger promotions. This **critical maintenance revert** addresses reports of staging or preview deployments being unintentionally promoted to production environments. The change ensures that setting production aliases via the CLI no longer triggers an unexpected deployment promotion, restoring the previous, safer behavior for users.

This commit **resolves an issue** within the **Vercel CLI's `alias set` command** where directly setting an alias to a production target could lead to unexpected rollbacks. It **enhances the command's behavior** by implementing a detection mechanism that, when a production alias is targeted, automatically triggers the appropriate **promote flow**. This **bug fix and feature enhancement** ensures that user intentions for promoting deployments are correctly handled, significantly improving the reliability and predictability of alias management for production environments.

This commit introduces a significant **user experience improvement** to the **CLI's project configuration process**. It **hides default project settings** from the user prompt when a **framework is automatically detected**, preventing the display of often unhelpful or confusing options. This **feature enhancement**, primarily affecting the `editProjectSettings` utility within the **CLI**, streamlines the initial setup for users by presenting a cleaner, more intuitive interface. The change ensures that while default settings are no longer prominently displayed, the option to modify them manually remains available, with corresponding updates to **CLI integration and unit tests**.

This commit introduces **new agent detection capabilities** within the `detect-agent` package, specifically extending the `determineAgent` logic. It **adds support for identifying Augment CLI Auggie** by checking the `AUGMENT_AGENT` environment variable and **detecting OpenCode** via the `OPENCODE_CLIENT` environment variable. This **feature enhancement** improves the system's ability to recognize various development environments, ensuring more accurate agent identification for downstream processes. Comprehensive unit tests have been included to validate these new detection mechanisms.

This commit introduces a **developer experience enhancement** to the **Vercel CLI**, specifically for **deployment** and **redeployment** operations. It adds **explicit feedback output** to the console when a production URL is successfully aliased, making the process more transparent for users. This new `Aliased` status message is integrated into both the `redeploy` command (`packages/cli/src/commands/redeploy/index.ts`) and the general `processDeployment` utility (`packages/cli/src/util/deploy/process-deployment.ts`), ensuring users are clearly informed about the aliasing action. This **feature enhancement** improves clarity for users running commands like `vc deploy --prod` by confirming the aliasing step. Unit tests have also been added to verify the correct display of this production domain aliasing feedback.

This commit implements a **bug fix** and temporary **maintenance** to resolve **failing tests** on the `main` branch. It **corrects** an issue in the `70-vercel-env-gatsby` **Gatsby test fixture** where environment variables were being truncated, ensuring proper test execution for the `static-build` package. To unblock the CI pipeline, it also **temporarily disables** specific **CLI integration tests** related to `api-env` and **Next.js end-to-end tests** by modifying the `test-e2e` script. This action stabilizes the `main` branch, with the understanding that the disabled tests will require follow-up investigation and re-enablement.

This commit **introduces a new `--json` flag** to the **Vercel CLI's `inspect` command**, providing a **new capability** for users to retrieve inspection results in a machine-readable JSON format. This enhancement to the **`inspect` command** facilitates scripting and automation by offering structured output. The implementation involves modifying the command's core logic in `packages/cli/src/commands/inspect/index.ts` to handle JSON serialization and updating its definition in `packages/cli/src/commands/inspect/command.ts`. Additionally, telemetry is added to track flag usage, and comprehensive unit tests are included to ensure the flag's correct functionality.

This commit performs **maintenance** by **updating the `pnpm-lock.yaml` file** for the **TanStack Start** project. It resolves an inconsistency where a previous pull request updated `package.json` dependencies but omitted the corresponding lockfile update. This ensures that the project's **dependency management** remains consistent, preventing potential build or runtime issues caused by mismatched package versions.

This commit **fixes a bug** within the **`vc build` command** where it was incorrectly ignoring entries specified in the **`.vercelignore` file** during local build processes. Previously, static assets, particularly those within the `/public` folder, would still be copied to `.vercel/output/static` despite being listed for exclusion. This **bug fix** ensures that `vc build` now properly respects `.vercelignore` rules, preventing unintended files from being included in the build output. The change improves the accuracy and efficiency of local development builds by aligning them with the intended deployment configuration.

This commit **fixes a critical bug** in the **Vercel CLI's `init` command** that caused project initialization failures. Previously, the `EXAMPLE_API` URL in `packages/cli/src/commands/init/init.ts` pointed to a protected `now-example-files.zeit.sh` endpoint, leading to a 401 error when running `vc init`. The URL has now been updated to `examples.vercel.sh`, resolving the authentication issue. This **bug fix** ensures the **CLI's core initialization functionality** operates correctly, allowing users to successfully set up new projects and improving the overall developer onboarding experience.

This commit **standardizes argument validation** for various `ls` and `list` subcommands across the **Vercel CLI**. It introduces a new shared utility function, `validateLsArgs`, which is then integrated into commands such as `alias ls`, `blob list`, `certs ls`, `domains ls`, and others. This **refactoring** effort ensures a **consistent user experience** by providing uniform error messages when invalid arguments are supplied, improving the overall robustness and predictability of the CLI. The change also includes new unit tests for the `validateLsArgs` utility and updates to existing command tests to reflect the standardized error output.

This commit **enhances the Vercel Node.js build system's warning messages** related to **Bun runtime** and the **Elysia framework**. It introduces a **new warning** that advises users to add `"bunVersion": "1.x"` to `vercel.json` when **Elysia is detected running with Node.js**, guiding them towards using Bun. Concurrently, an **outdated warning** about Bun not being supported at runtime is **removed**, reflecting current platform capabilities. This **feature enhancement and maintenance** provides clearer guidance for developers using **Elysia and Bun-based projects** on Vercel.

This commit performs a **maintenance task** by **temporarily disabling specific failing integration tests** within the **Next.js testing suite**. It targets tests related to **static metadata deployment, probe checks, and Prerender outputs** in the `next` package, which were consistently failing on the `main` branch. By adding `.skip` to these tests, the change aims to improve **CI stability** and prevent unrelated build failures, allowing for a clearer focus on other development efforts.

This commit **enhances framework detection logic** to correctly prioritize **Nitro** over Vite when both are present in an application. Previously, such applications were misidentified as Vite, but now the system will accurately recognize them as **Nitro-based**. This **configuration adjustment** in `packages/frameworks/src/frameworks.ts` ensures that tooling and internal processes interact with these projects under the correct framework context, improving overall system accuracy for hybrid applications.

This commit introduces a **new example application** for the **Elysia web framework**, expanding the available `examples` within the project. It provides a complete, deployable Elysia application, including its core `src/index.ts` implementation, `package.json` dependencies, and Vercel-specific configuration in `vercel.json`. This **feature addition** enables users to quickly initialize new Elysia projects using `vc init elysia` and serves as a reference for deploying Elysia applications on Vercel, validated by a new `elysia.test.ts` integration test.

This commit provides a **documentation fix** for the **TanStack Start** example, specifically addressing an inaccuracy in its `README.md` file. It updates the development command from the incorrect `pnpm start` to the correct `pnpm dev`, ensuring users can successfully run the application. This **maintenance** change improves the initial setup experience for developers creating new `TanStack Start` projects via `npm create @tanstack/start@latest`, preventing common startup issues.

This commit **removes React-specific favicon and associated assets** from the **TanStack Start example project**. This **maintenance** task addresses an issue where deployment platforms, such as Vercel, would incorrectly display the React icon instead of the intended TanStack icon. By eliminating the conflicting React assets, the example now correctly reflects the **TanStack brand identity**, ensuring a consistent visual experience for users. This **fix** improves the branding and user perception of the `TanStack Start` starter template.

This commit performs **release preparation** by adding a new changeset entry to ensure proper version bumps for the **`vercel` CLI** and **`@vercel/client`** packages. It rectifies an oversight from a previous pull request that failed to trigger a new CLI release. The primary impact is to facilitate a new **CLI release** that officially incorporates and supports the recently added **TanStack Start framework preset**, making it available to users.

This commit **introduces a new framework preset** for **TanStack Start**, enabling Vercel to correctly detect and optimize deployments for applications built with this framework, which previously defaulted to a generic Vite detection. This **new capability** is supported by a **comprehensive example application** located in `examples/tanstack-start/`, demonstrating various features like SSR, API routes, and server functions. A dedicated **integration test** (`examples/__tests__/integration/tanstack-start.test.ts`) has also been added to validate the proper deployment and functionality of **TanStack Start** projects. This **enhances Vercel's platform support** by providing first-class recognition and a robust reference for developers using **TanStack Start**.