Nik

This commit introduces a **new capability** for **worker services**, enabling a single worker to subscribe to and process messages from **multiple topics**. This enhancement required updating the `vercel.json` configuration schema to accept an array of topics, and modifying the **queue broker** logic within `packages/cli/src/util/dev/queue-broker.ts` to correctly manage consumer groups and dispatch messages. Changes also span **build utilities**, **service detection**, and **CLI display** to properly handle and visualize multi-topic configurations. This provides greater flexibility for common worker patterns, simplifying deployment and management by consolidating related message processing into a single service.

This commit introduces a **new capability** for **experimental services**, allowing users to specify a custom `envPrefix` in their configuration. This prefix will be used when injecting service URL environment variables, such as `MY_APP_API_URL`, into individual services. The change impacts the **build-utils**, **CLI**, **config**, and **fs-detectors** modules, modifying type definitions, configuration resolution, and the logic for generating environment variables. This enhancement improves **environment variable management** and organization for multi-service deployments by providing greater control over injected variables.

This commit introduces a **new capability** that allows multiple **services** to share the same underlying source code, significantly simplifying configurations where similar services (e.g., worker services) require distinct setups without duplicating files. It achieves this by extending the `BuildOptions.service` interface with a `name` property and modifying the **Python builder** (`packages/python/src/index.ts`) to create isolated, service-specific virtual environments. This **enhancement** prevents dependency conflicts and reduces boilerplate, improving the developer experience for projects with complex service architectures, particularly those leveraging **Python services**.

This commit **corrects the release configuration** for the **`@vercel/python-workers`** package. It **adjusts the intended release type** from `minor` to `patch` within the `.changeset/tough-chefs-brake.md` file. This **maintenance fix** prevents an unintended minor release of a package that is still under active development, ensuring its versioning accurately reflects its current status and avoiding premature public exposure of incomplete features.

This commit introduces a **new capability** to the **`vercel-workers` Python package**, enabling seamless serialization of common non-standard library types within task payloads. It specifically adds support for `uuid.UUID`, `decimal.Decimal`, and `datetime.date`/`datetime.datetime` when using the `send()` function. For most brokers, this is implemented via a custom, overridable `WorkerJSONEncoder` in `client.py`, while the **Django backend** in `django/backend.py` extends `django.utils.normalize_json` to handle these types. This enhancement significantly improves the developer experience by allowing these complex data types to be passed directly, with comprehensive test coverage added across various broker integrations including Dramatiq, Django, and Celery.

This commit **increases the startup timeout for Python development servers** from 10 seconds to 5 minutes. This **configuration adjustment**, primarily in `packages/python/src/start-dev-server.ts`, is a **maintenance fix** designed to prevent premature startup failures for Python applications that require more time to bootstrap. By aligning the `DEV_SERVER_STARTUP_TIMEOUT` with the orchestrator's existing limits, it **improves the reliability and developer experience** for complex Python services during their initial setup phase.

This commit introduces a **new end-to-end test case** to validate the functionality of **worker services** when configured with **wildcard topics**. It addresses a gap in the existing test suite by adding a comprehensive fixture under `packages/fs-detectors/test/fixtures/e2e/14-services-worker-wildcard-topic/` that simulates a Flask application and a Dramatiq worker consuming messages via a wildcard topic. This **maintenance** effort ensures the continued reliability and correct behavior of this supported `services` feature, preventing potential regressions in how workers process messages from dynamically matched topics. The added test fixture includes `app.py`, `probes.json`, `pyproject.toml`, `vercel.json`, and worker-specific files like `broker.py` and `tasks.py`.

This commit introduces a **new capability** to `vc dev`, enabling the local development and testing of **Python worker services**. It achieves this by implementing an **in-memory queue broker** (`queue-broker.ts`) and a **dev proxy** within the `packages/cli`'s development server, which emulates the Vercel Queues API. This allows developers to run and debug worker services locally without requiring any code changes, facilitating a seamless transition from local development to deployment on Vercel. The changes are strictly confined to the local development environment, ensuring no impact on production systems or security.

This commit introduces **support for Python cron services** within the **`vc dev` local development server**, enabling developers to schedule and trigger cron jobs locally. It implements **new scheduling and triggering logic** in the **services orchestrator** to manage cron job timers and HTTP requests, alongside **updates to the Python runtime** for correct cron service detection and execution. The **`vc dev` display logic** is also enhanced to sort services by type (web and cron) and present a cleaner output by avoiding internal URLs. This **new capability** significantly expands the local development experience, allowing for comprehensive testing of Python cron services.

This commit **refactors** the **Python dev server** initialization by moving most of its core logic from the `vc_init_dev.py` shim into the `vercel-runtime` package. This **restructuring** introduces new modules within `vercel-runtime` for app detection (`resolver.py`), route prefix handling (`routing.py`), and the main server startup and logging (`dev.py`). The change significantly **reduces the complexity** of the `vc_init_dev.py` shim and makes the **Python development environment more self-contained**. A notable benefit is that users no longer need to separately install `werkzeug` or `uvicorn` to run `vc dev`, as these are now vendored within the runtime.

This commit **adds a new capability** for defining **Python cron service entrypoints** using a `module:function` string format, allowing users to explicitly specify a particular function within a module as the cron handler. This **feature addition** involves updates to **`build-utils`** for type definitions, **`fs-detectors`** for parsing and validation, **`python-analysis`** for callable detection, and **`vercel-runtime`** for bootstrapping these new entrypoints. It introduces an **optional `handlerFunction` property** to the service configuration, providing a more precise and flexible way to configure cron handlers. This **enhances the developer experience** for **Python cron services** by offering explicit control over the execution entrypoint.

This commit introduces a **new capability** by adding **support for Python worker services utilizing Django tasks**. It extends the **Python worker runtime** to allow Django tasks to function as background worker services, alongside existing support for Celery and Dramatiq. Specifically, the `vercel_runtime/workers.py` module gains a new `_bootstrap_django_worker_app` function and updates the main worker service bootstrap logic to integrate this framework. This enhancement provides Python developers with greater flexibility in choosing their preferred task queue framework for worker deployments, validated by new end-to-end test fixtures.

This commit **refines the service auto-detection logic** within the `fs-detectors` package to **skip auto-detection for root-only projects** that do not contain explicit backend services. Specifically, the `detectServicesAtRoot` function in `packages/fs-detectors/src/services/auto-detect.ts` is modified to return null services in these scenarios, preventing misclassification. This **logic change** ensures that single root-only framework projects are no longer incorrectly identified as services, leading to more accurate project analysis. The update is validated by new and updated unit tests in both `packages/cli` and `packages/fs-detectors`, confirming the expected behavior for such project structures.

This commit introduces a **new capability** by adding **support for Python background worker services**, specifically **Dramatiq and Celery**, enabling them to run as serverless functions backed by Vercel Queues. It integrates the `vercel-workers` PyPI package into the **Python runtime** (`vercel-runtime`), which provides custom transports and automatically bootstraps user worker apps into ASGI applications via `workers.py`. The **Vercel CLI** and **`fs-detectors`** packages are updated to correctly identify, route, and manage these new `worker` service types, ensuring seamless deployment and local development. This feature significantly expands Vercel's offerings for Python developers needing robust background task processing, including automatic installation of required dependencies and handling of Vercel-specific headers.

This commit **improves logging configuration** for **Python web servers** used within the **`vc dev` environment**, addressing issues where all logs defaulted to `stderr`. It introduces a **new capability** to route log messages based on their severity: `WARNING` level and below are now directed to `stdout`, while `ERROR` level and above are sent to `stderr`. This **maintenance improvement** ensures that informational logs do not incorrectly appear as errors, enhancing clarity for developers. Additionally, the `services-orchestrator` is updated to include stream labels in debug mode, further aiding log interpretation from services like `uvicorn`, `hypercorn`, and `fastapi_cli`.

This commit delivers a **bug fix** addressing a **dev server hang** that occurred when using **FastAPI CLI** in multi-service mode. The hang was caused by the `rich` library attempting to query terminal colors, which could block if another service simultaneously read from the terminal. To resolve this, the `startService` and `startDevServer` functions in `packages/cli/src/util/dev/services-orchestrator.ts` and `packages/python/src/start-dev-server.ts` now spawn child processes in **detached mode** with **ignored stdin**. This ensures `rich` uses default colors, preventing the hang, and also passes the `COLUMNS` environment variable for proper terminal width formatting, significantly improving the stability of the **development environment** for Python services.

This commit **fixes a critical bug** in the **Python dev server** that caused crashes when projects utilized **relative imports** within a Python package serving as the entrypoint. It resolves this by adapting the `vercel-runtime`'s approach, specifically modifying the dev shim (`vc_init_dev.py`) to use `spec_from_file_location` for module imports and adjusting `PYTHONPATH` construction within `start-dev-server.ts`. This **bug fix** ensures the **development environment** correctly handles module resolution for Python packages, preventing crashes and improving the reliability of local Python development. The change primarily affects the **`packages/python` module** and its internal tooling for server startup.

This commit **refactors** how **experimental services** are enabled within the Vercel **CLI**, making the `experimentalServices` configuration in `vercel.json` the primary marker. Previously, an environment variable was strictly required; now, `vercel.json` can directly activate these features. Consequently, the `VERCEL_USE_EXPERIMENTAL_SERVICES` environment variable is now specifically used to enable auto-discovery of services. This **feature flag behavior change** simplifies configuration for users and involves updates to the `dev` command and service detection utilities, including making detection functions asynchronous.

This commit introduces a new **`--local` flag** for the **`vc dev` command**, enabling users to run the development server without linking to a Vercel project or requiring an authentication token. This **feature addition** streamlines local development workflows by allowing `vc dev` to start without any additional setup prompts. It **refactors** an existing experimental environment variable (`VERCEL_EXPERIMENTAL_DEV_SKIP_LINK`) into a formal CLI option, impacting the **CLI's token handling logic** and **telemetry** for the `dev` command. The change provides a more explicit and user-friendly way to manage local development environments independently of Vercel project configurations.

This commit introduces a **new experimental capability** to the Vercel CLI, allowing users to **skip authentication and project linking** for the `vc dev` command. By setting the `VERCEL_EXPERIMENTAL_DEV_SKIP_LINK` environment variable, developers can now quickly prototype or test examples without needing to authenticate or create a Vercel project. This **enhances the local development workflow** by removing setup friction, primarily affecting the `packages/cli` module's `dev` command and its authentication flow. It's an opt-in feature designed for convenience, deliberately bypassing standard security for local development.