Mark Knichel

This commit introduces **new CLI commands** to the **`@vercel/cli`** for comprehensive **microfrontend group management**. Users can now **create, delete, add projects to, and remove projects from microfrontend groups** directly via the command line using `vc microfrontends create-group`, `add-to-group`, `remove-from-group`, and `delete-group`. This **new capability** provides a developer-centric workflow, allowing local configuration of `microfrontends.json` interactively for `create-group` and reducing reliance on the UI for setup and ongoing management. Additionally, a minor **refactoring** centralizes the `openUrlInBrowserCommand` utility function across the CLI.

This commit introduces **new helper functions** (`matchers.header`, `matchers.cookie`, `matchers.query`, `matchers.host`) within the **`@vercel/config`** package to streamline the definition of `has` and `missing` conditions for **routing rules**. These functions serve as a **developer experience enhancement**, reducing boilerplate by providing a more ergonomic way to construct `Condition` objects in configuration files. This **new capability** simplifies the creation of complex routing logic, making configurations cleaner and more readable. The change is fully backward compatible, ensuring existing raw `Condition` object definitions continue to function as before, with updated examples demonstrating the new, simplified syntax.

This commit **adds new documentation** to the **Vercel CLI** project, introducing `packages/cli/AGENTS.md`. This new guide provides essential instructions and best practices specifically for **coding agents** that are designed to create or modify CLI commands. The **documentation addition** aims to ensure consistency and adherence to conventions for AI-generated contributions to the CLI. This **maintenance** task also updates `packages/cli/CLAUDE.md` to reference the newly created `AGENTS.md` file, streamlining guidance for agent development.

This commit introduces a **new capability** to the **Vercel CLI**, significantly enhancing the `vercel rolling-release configure` command. It now provides **interactive and flag-based configuration** for rolling releases, removing the previous requirement for users to manually craft JSON. This **usability improvement** allows users to easily enable/disable rolling releases, define advancement types, and specify deployment stages directly via new CLI flags such as `--enable`, `--advancement-type`, and `--stage`, or through an interactive prompt. The core logic for parsing and validating these configurations is implemented in `configure-rolling-release.ts`, and new telemetry tracks the usage of these flags, ultimately simplifying the management of rolling deployments for all users.

This commit **enhances the Vercel CLI's user experience** by making the `redirects` command discoverable in the top-level help output. It **fixes a discoverability issue** where `vercel -h` previously omitted the `redirects` command, preventing users from easily finding it. This **CLI feature enhancement** updates the `packages/cli/src/args.ts` module to include `redirects` in the help message, improving **user guidance** and command awareness. The change is reflected in updated snapshot tests for the CLI's help output.

This commit introduces a **new feature** to the **Vercel CLI**, adding the `vercel redirects upload` command to facilitate **bulk uploading of redirects**. Users can now upload redirects from CSV or JSON files, with the CLI performing client-side validation, displaying a diff of the changes, and offering a prompt for promotion. This enhancement significantly improves the **redirects management workflow** by providing an efficient way to update large sets of redirects, affecting the `packages/cli` module and its interaction with the Vercel platform. It also includes new utility functions for validation (`validate-redirects.ts`) and updates telemetry to track usage of the new command.

This commit introduces a **non-interactive mode** for the `vc redirects add` command within the **CLI's redirect management subsystem**, enabling users to specify redirect properties such as status code, case sensitivity, and query parameter preservation directly via command-line flags. It also **refactors** the `--staged` flag to `--staging` across `redirects` commands and enhances `vc redirects ls --staging` to display a diff of staging redirects against production. Additionally, a **bug fix** is applied to the `isValidUrl` utility function, ensuring correct validation of both relative paths and absolute URLs. These updates collectively improve the **CLI's redirect configuration workflow** and overall user experience.

This commit introduces a **new capability** to the **Vercel CLI** by adding a comprehensive set of commands for the upcoming **bulk redirects feature**. Users can now manage project-level redirects through `vercel redirects`, including subcommands like `add`, `remove`, `list`, `list-versions`, `promote`, and `restore`. This significantly enhances redirect management by allowing changes independent of deployments, affecting the `packages/cli` module with new command implementations, API utility functions, and extensive unit tests. The feature is currently gated and will display an error until enabled for a team, providing a robust foundation for future redirect management.

This commit **enhances** the **`@vercel/routing-utils`** package by **increasing the maximum allowed length for header values** within its routing schemas. Previously, the validation logic limited header values in configuration files like `vercel.json` and `next.config.js` to 4KB. This **feature enhancement** now permits header values up to **32KB**, aligning the internal validation with the Vercel CDN's actual capabilities. Developers can now define more extensive or complex header configurations without encountering validation errors, improving flexibility for advanced routing setups.

This commit introduces a **new capability** to the **Firewall rate limiting** module, enabling the specification of an optional path prefix for rate limit API requests. This feature, configured via an environment variable, is crucial for supporting **microfrontend architectures** and applications that utilize rewrites, ensuring requests are correctly routed to the appropriate backend. The `checkRateLimit` function within `@vercel/firewall` is updated to incorporate this prefix, and new end-to-end tests validate its functionality. This enhancement simplifies integration for complex deployment patterns, particularly when used in conjunction with `@vercel/microfrontends`.

This commit **fixes a critical bug** preventing the **microfrontends local development proxy** from starting on **Windows**. Previously, Turborepo attempted to execute `.js` scripts directly, relying on shebangs which are unsupported on Windows, leading to a "not a valid Win32 application" error. The change modifies the **Turborepo task execution logic** within `crates/turborepo-lib/src/task_graph/visitor/command.rs` to explicitly invoke `node` for these scripts. This ensures that **Windows users** can now successfully run `pnpm turbo run dev` in microfrontends repositories, resolving a critical startup failure.

This commit introduces a **new feature** to the **Vercel CLI**, enabling it to persist the `projectName` within the local `.vercel/project.json` file. The **project linking and pulling utilities** are updated to store this identifier when a project is linked or its settings are pulled, specifically affecting `linkFolderToProject` and `writeProjectSettings`. This enhancement is crucial for **microfrontends in local development**, as it will facilitate correct configuration discovery and enable more informative error messages.

This commit **enhances** the **Vercel CLI's `microfrontends pull` command** by modifying its configuration fetching logic. It now **prioritizes retrieving microfrontends configuration directly from the project ID** when a specific deployment ID is not explicitly provided. This **fixes a bug** where new projects added to a microfrontends group would encounter an error when attempting to pull their configuration before a new deployment was created. The change improves the **reliability and developer experience** for managing microfrontends, particularly during initial project setup, by making the `pull` operation more robust.

This commit **enhances Turborepo's command resolution** by updating the `provide_command` function within the `turborepo-lib` crate. Specifically, it modifies the **command provider** to correctly identify and execute the `microfrontends` binary by removing the expectation for a hyphen in its name. This **feature enhancement** aligns Turborepo with standard microfrontend naming conventions, ensuring that tasks involving the `microfrontends` binary are properly recognized and executed. The change **improves compatibility** for projects that utilize this common binary naming scheme.