Thomas Knickman

This commit **introduces a new telemetry feature** to the **CLI** that tracks whether `stdin` is connected to a TTY (terminal). It **enhances the telemetry system** by adding a `trackStdinIsTTY` method to both the `TelemetryClient` and `RootTelemetryClient` within `packages/cli/src/util/telemetry`. The main CLI entry point in `packages/cli/src/index.ts` is updated to invoke this new tracking method. This **new capability** provides valuable data on how the CLI is being used, distinguishing between interactive and scripted executions. **Unit tests** have been added in `packages/cli/test/unit/telemetry/stdin-is-tty.test.ts` to validate the correct functioning of this new telemetry event.

This commit **enhances the CLI telemetry system** by **integrating `user_id` into all telemetry events**. The `TelemetryEventStore` in `packages/cli/src/util/telemetry/index.ts` is updated to manage and include this new identifier, ensuring it's present during event initialization and saving. This **feature addition** provides more granular insights into CLI usage, with corresponding updates to test matchers like `toHaveTelemetryEvents` to validate the presence of `userId` in collected data.

This commit performs an **internal tooling update** by **refactoring** the git user name from `vercel-release-bot` to `vercel-cli-release-bot` within several utility scripts. Specifically, it affects the `utils/update-gatsby-fixtures.js`, `utils/update-next.js`, `utils/update-remix-run-dev.js`, and `utils/update-turbo.js` scripts. This **maintenance** task ensures that automated updates for Gatsby, Next.js, Remix, and Turbo fixtures and dependencies are correctly attributed to the new bot identity in the **CI/CD pipeline**. The change is entirely **internal** and has no impact on user-facing features or product functionality.

This commit introduces a **new capability** to the **CLI's API request utility**, enabling it to send an `x-ai-agent` header with the agent's name on all API requests. This **feature addition** ensures that when the CLI operates under an AI agent, backend services can properly identify the source of the request. The change primarily affects the `request` function within `packages/cli/src/util/client.ts`, modifying how API calls are made. This allows for better tracking and potential agent-specific handling of requests originating from the CLI.

This commit performs a **maintenance chore** by **updating the GitHub token** used across numerous **GitHub Actions CI workflows**. It replaces the generic `GH_TOKEN_PULL_REQUESTS` with the more specific `VERCEL_CLI_RELEASE_BOT_TOKEN` in files like `cron-update-gatsby-fixtures.yml`, `release.yml`, `test-e2e.yml`, and `test-lint.yml`. This **infrastructure change** ensures that automated tasks, including fixture updates, testing, and releases, continue to authenticate correctly and securely within the CI/CD pipeline. The update impacts the **reliability and security** of the project's automated build and deployment processes by using a token specifically designated for the release bot.

This commit **reverts** the "Env pull local changes preview" feature, rolling back recent enhancements to the **Vercel CLI's `env pull` command**. Specifically, it **removes** the logic for previewing local environment variable changes and associated confirmation prompts from `packages/cli/src/commands/env/pull.ts`, along with the `getDownloadedEnv` helper function. This **rollback** also impacts the `packages/cli/src/util/env/diff-env-files.ts` utility, effectively **undoing** its recent enhancements for detecting and displaying removed environment variables and updating delta string formatting. As a result, the `env pull` command no longer offers this interactive preview, and **related unit tests** in `packages/cli/test/unit/commands/env/pull.test.ts` have been removed to reflect the change.

This commit introduces a **new feature** to the **Vercel CLI**, adding a comprehensive `crons` command for managing cron jobs. Users can now **list existing cron jobs** (`crons ls`), **add new ones** with schedule validation and automatic `vercel.json` modification (`crons add`), and **manually trigger specific cron jobs** (`crons run`). This significantly enhances the **developer experience for cron job management** by providing direct command-line control. The change includes extensive unit tests for all subcommands and integrates new **telemetry** to track command usage.

This commit significantly **enhances** the **Vercel CLI** by introducing an **interactive mode** for the `vercel webhooks create` command, which now interactively prompts users for webhook URLs and event selections when run without arguments. It also **improves output formatting** by fixing column alignment in webhook creation results, replacing tab characters with `padEnd(10)` for better consistency. Furthermore, a global **maintenance change** updates the warning prefix across all **CLI output** from `WARN!` to `WARNING!`, ensuring clearer messaging. These changes collectively **improve the usability and consistency** of the CLI, particularly for webhook management.

This **maintenance chore** significantly **enhances code quality and consistency** by **enabling additional Biome linter rules** across the project. It updates the **CI/CD pipeline's Biome configuration** to enforce new correctness, style, complexity, and security checks. The commit also applies numerous **autofixes** throughout various `packages` like `cli`, `next`, and `node`, simplifying expressions, removing redundant code, and renaming variables for clarity. Additionally, `biome-ignore` comments are introduced in specific test and schema files to accommodate intentional patterns, ensuring a cleaner codebase without functional changes.

This commit performs **maintenance** and **code cleanup** by **removing obsolete ESLint disable comments** from various source files and test suites across the project. This action is a direct follow-up to the migration to Biome as the primary linter, ensuring that no legacy ESLint directives remain. It affects numerous **packages** such as `build-utils`, `cli`, `next`, and `node`, along with updates to **CI workflows** in `.github/workflows/test-lint.yml` and the `biome.jsonc` configuration. The change streamlines code quality checks, reduces technical debt, and aligns the codebase with the new linting standard, improving overall code consistency.

This commit executes a significant **tooling migration**, completely **removing ESLint** from the monorepo to establish **Biome as the sole linter**. It updates the **linting infrastructure**, including CI workflows, `lint` scripts, and `lint-staged` configurations, to exclusively use Biome, while all ESLint-related dependencies and configuration files are deleted. Specific ESLint rules like `no-console` and `consistent-type-imports` are migrated and scoped within `biome.jsonc` for the `packages/cli` module, and `eslint-disable` comments are replaced with `biome-ignore` directives in affected files. This **maintenance** effort streamlines the project's linting setup, reducing overhead and standardizing code quality checks across the codebase.

This commit **enforces Biome linting as a blocking CI check**, significantly improving code quality and consistency across the project. It **refactors** 76 files by auto-fixing 117 Biome violations, primarily by prefixing unused variables (e.g., `catch (e)` to `catch (_e)`), removing unused imports, and adding ignore comments for intentionally skipped tests. Additionally, it **exports the `AuthConfig` interface** from `internals/types` and **excludes specific test fixtures** from Biome's scope. This broad **maintenance** effort ensures future code adheres to stricter linting standards across numerous **packages and utilities**, impacting the **CI/CD pipeline** and overall codebase health.

This commit performs a **tooling migration**, replacing **Prettier** with **Biome** as the primary code formatter across the project. It updates the **CI/CD pipeline** by modifying `.github/workflows/test-lint.yml` to use Biome for format and lint checks, and adjusts the `lint-staged` configuration in `package.json`. This **maintenance chore** also includes a widespread **cosmetic reformatting** of numerous test files and a CSS file across various packages (e.g., `packages/cli`, `packages/fs-detectors`, `packages/functions`) to conform to Biome's styling rules, ensuring consistent code style enforcement.

This commit **integrates the Biome linter** into the project's **Continuous Integration (CI) workflow** as a **non-blocking check**. It **updates the `test-lint.yml` workflow** to include an informational Biome step, ensuring it doesn't fail builds initially. Concurrently, the **`biome.jsonc` configuration** is adjusted to include more file types, exclude test fixtures, and disable rules already covered by ESLint, allowing the initial run to pass. This **tooling update** is a **maintenance chore** aimed at improving future code quality without impacting application functionality or blocking development.

This commit **introduces Biome** as a new code quality tool, integrating it into the project's **CI/tooling infrastructure**. It adds a `biome.jsonc` configuration file with initial formatter and linter rules, and updates `package.json` to include `@biomejs/biome` as a dev dependency and a `biome:check` script. This **maintenance chore** is a **new capability** for code style enforcement, currently configured as a "noop" to prevent immediate breaking changes. The change has **no impact on application logic or security**, focusing solely on enhancing the **developer experience** and future code consistency.

This commit introduces a **new capability** to the **Vercel CLI's `ls` command**, enabling users to list deployments across multiple projects. It adds an `--all` flag to explicitly show deployments from all projects and modifies the default behavior so that `vercel ls` no longer requires a linked project, instead listing all deployments in the current scope when unlinked. This **enhancement** to the **`list` command** improves deployment visibility and management by adding a "Project" column to the output table and integrating **telemetry tracking** for the new flag.

This commit introduces a **bug fix** and **UX improvement** to the **CLI**'s **upgrade prompt** functionality. It **gracefully handles `SIGINT` (Ctrl+C) interruptions** by wrapping the upgrade confirmation prompt in a try-catch block within `packages/cli/src/index.ts`. This prevents unsightly stack traces from being displayed when a user force-closes the prompt, ensuring a cleaner and more robust user experience for the **CLI**.

This commit delivers a **bug fix** for the **CLI's login command**, specifically addressing errors encountered when opening a browser in headless environments. It implements robust error handling for the subprocess responsible for browser invocation, ensuring graceful failure instead of silent crashes. Additionally, this change introduces **new testing infrastructure**, including a `Dockerfile.headless` and `test-headless.sh` script, to enable dedicated and repeatable headless CLI testing. This improves the reliability of the **CLI login process** and provides essential tools for validating its behavior in automated or non-graphical settings.

This commit implements a **feature enhancement** to the **CLI login command**, specifically in `packages/cli/src/commands/login/future.ts`, to provide a **smoother authentication experience** by automatically opening the browser for device authorization. It eliminates the need for manual user input during login and includes detection for specific agents like Cursor to intelligently control this behavior. Furthermore, the change incorporates graceful fallback instructions, significantly improving the **user experience** for agentic logins.

This commit delivers a **bug fix** for the **Vercel CLI** by correcting a critical dependency configuration. It **moves the `proxy-agent` package from `devDependencies` to `dependencies`** within `packages/cli/package.json`. This change resolves a `TypeError: ProxyAgent is not a constructor` that occurred at runtime, which previously prevented the `vercel build` command from executing successfully. The fix ensures that the necessary `proxy-agent` module is available during CLI operations, restoring the **build functionality** for users.