Ricardo Gonzalez

This commit **fixes** a reliability issue in the **Go runtime environment** by updating the `waitForServer` function within `packages/go/vc-utils.go`. Previously, `waitForServer` would ping the root HTTP endpoint (`/`) to check for server readiness, which was problematic due to potential non-existence, side effects, and lack of time-bounding. The function now employs **TCP dialing with `net.DialTimeout()`** to directly and robustly probe listener readiness. This change primarily impacts **Go applications** using the "Go" preset or `experimentalServices`, ensuring a more accurate and efficient server startup process.

This commit **enhances the error reporting** for failed `go build` commands by capturing and including the `stderr` and `stdout` output from the Go compiler. Previously, build failures only displayed a generic "Command failed" message, offering no insight into the root cause. Now, the **Go command execution helper** within `packages/go/src/go-helpers.ts` provides detailed compiler errors, such as undefined symbols, directly in the error message. This **improves the developer experience** by offering immediate and actionable feedback, significantly streamlining the debugging process for Go projects.

This commit **corrects a dependency misconfiguration** within the **`@vercel/fs-detectors`** package, promoting `@vercel/build-utils` from `devDependencies` to `dependencies`. This **dependency fix** addresses a runtime regression where `detectServices()` would fail in the API CI due to the unavailability of essential helpers like `isNodeBackendFramework()`. By ensuring `build-utils` is present at runtime, this change resolves the issue introduced in version 50.33.1 and guarantees the proper functioning of the `fs-detectors` module.

This commit **refactors** the **Python Celery worker integration** to simplify how Celery worker services are declared and configured, aligning it more closely with standard Celery usage. Developers can now import `Celery` directly from the `celery` package and explicitly set the `broker` URL, with `vercel://` automatically configured as the default for Vercel Queues. This involves significant internal **refactoring** within the `vercel-runtime` and `vercel-workers` packages to manage environment setup and transport aliases, removing custom `Celery` classes and hardcoded versions. Although this introduces a **breaking change** for the currently undocumented Python worker services, it provides a cleaner and more flexible API for future development and simplifies the user experience for Vercel Queues.

This commit introduces a **new capability** to the **CLI project linking flow**, enabling the **auto-configuration of `experimentalServices`** within `vercel.json`. It enhances the user experience by intelligently detecting multiple services within a project's layout and interactively prompting the user to confirm or select which services to configure. This **streamlines the initial setup process** for multi-service repositories, automatically generating the necessary `experimentalServices` configuration based on inferred project structure. The changes primarily affect the `vercel link` command, improving user guidance and reducing manual `vercel.json` configuration for complex projects.

This commit introduces a **new capability** for **Node.js services** within the `backends` build system, implementing a bootstrap shim to automatically **strip the service route prefix** from incoming requests. This **alignment** ensures consistent request handling behavior across all service runtimes, matching the existing functionality for Python, Go, and Ruby builders. The change simplifies routing logic for Node.js developers by abstracting away the service prefix, improving the developer experience for experimental backends builds. New modules like `service-vc-init.ts` handle the shim creation and application, while comprehensive **unit and end-to-end tests** have been added or updated to verify this functionality across various Node.js frameworks such as Express, Koa, and Hono.

This commit implements a **major infrastructure change** by switching the default framework preset for **Node.js services** from `@vercel/node` to the new `@vercel/backends` builder. This **feature enhancement** significantly modifies core **build infrastructure** and **service resolution logic**, enabling advanced capabilities such as service route prefixing, destination remapping, and service name propagation through build configurations. The **`@vercel/backends`** package now includes new logic for route manipulation and output path normalization, while the **`fs-detectors`** package is updated to correctly infer runtimes and select the new builder for Node.js web services. This **high-risk change** impacts how Node.js applications are built and deployed, ensuring improved integration and functionality within the Vercel platform.

This commit **fixes broken CI** by resolving Python wheel URL issues that caused `vercel-runtime` dependency failures in the `test.yml` workflow. It integrates the existing "Resolve Python wheel URLs" mechanism, previously only present in `test-e2e.yml`, into the main test workflow to ensure Python builds can correctly find and install packages. Additionally, the `testFixtureStdio` utility in `packages/cli/test/dev/utils.ts` is updated to pass these resolved Python-related build environment variables to `vercel deploy` commands during tests. This **maintenance** change ensures the **Python runtime testing** suite runs reliably and accurately.

This commit implements a **critical fix** to the **service routing mechanism** by **excluding known service route prefixes from subdomain rewrites**. It modifies the logic within `packages/fs-detectors/src/services/detect-services.ts`, specifically impacting `generateServicesRoutes` and `getExplicitHostPrefixNegativeLookahead`, to ensure that canonical service paths like `/_/api` are correctly preserved. This **enhancement** resolves an issue where services accessed from a different subdomain would fail to reach their intended backend, preventing broken API calls. Consequently, **services are now globally accessible at their defined route prefixes across all hosts**, significantly improving the reliability of multi-service deployments.

This commit **promotes the Go frameworks preset** by removing its `experimental` flag from the configuration within the **`@vercel/frameworks` package**. This **feature flag change** signifies that **Go framework support** is now considered stable and ready for general availability, moving it out of an experimental state. The update indicates increased confidence in the stability and functionality of Go projects on the platform. A new changeset file, `tiny-terms-boil.md`, was added to document a patch version bump for the package.

This commit introduces a **new capability** within the **`fs-detectors` package** by enhancing the `detectBuilders` function. It now allows the system to build using `experimentalServices` **regardless of the detected framework setting**, providing greater flexibility for build configurations. This change enables service-based builds even when no specific framework is identified, broadening the applicability of experimental features. A new test case has been added to verify that `detectBuilders` correctly utilizes `experimentalServices` in these scenarios.

This commit **fixes a flaky CI test** within the **`fs-detectors`** package, specifically addressing intermittent failures in `test/unit.local-file-system-detector.test.ts` related to Unix socket handling. The **test fix** resolves issues caused by shared temporary directories and missing async error handling for `server.listen()` bind operations. It achieves this by utilizing `fs.mkdtemp()` for unique test environments, implementing robust error handling with `server.once('error', reject)`, and improving cleanup procedures. This **maintenance** work significantly enhances **CI stability** and reliability for the `fs-detectors` module's unit tests.

This commit **adds support for Go versions 1.25 and 1.26** to the `packages/go` builder, updating the internal version map in `go-helpers.ts` and bumping patch versions for Go 1.23 and 1.24. It introduces **new integration test fixtures** for `gin`, `net/http`, and `chi` servers specifically for Go 1.25 and 1.26, ensuring compatibility with these new runtimes. Additionally, the **test infrastructure has been refactored** to split integration tests into chunked files, improving test execution efficiency. This **new capability** allows users to deploy applications built with these newer Go versions, while the test changes ensure robust validation of the Go builder.

This commit introduces **subdomain support for experimental services**, allowing users to define a `subdomain` field in their `experimentalServices` configuration. This **new capability** automatically generates host-based rewrite routes, mapping `subdomain.*` to the service's `routePrefix`. It affects **service configuration schemas**, **type definitions** in `build-utils` and `config`, and the **routing logic** within `fs-detectors` and the `cli`'s development server. The change includes robust validation for the `subdomain` field, ensuring proper DNS label format and restricting its use to appropriate service types, thereby enabling more flexible routing for experimental services.

This commit introduces a **new capability** by implementing **support for scheduled Python cron worker services**, allowing users to define and execute background tasks via `vercel.json` configurations. It involves significant updates to the **Python runtime** to bootstrap and securely execute entrypoints with `if __name__ == '__main__'` guards, wrapping them in a lightweight ASGI app. The **service detection logic** (`fs-detectors`) is updated to generate internal routes for these cron services, which are protected by **CRON_SECRET authentication** using timing-safe comparison. This feature expands the types of Python applications deployable on Vercel, enabling robust and secure scheduled job execution.

This commit introduces a **feature enhancement** to the **Vercel CLI**'s version reporting, specifically addressing difficulties in identifying the CLI version within build containers. It modifies the `packages/cli/src/index.ts` file to **conditionally print the Vercel CLI version to standard output** when the `VERCEL=1` environment variable is set, which typically indicates execution within a Vercel build environment. Otherwise, the version information continues to be logged as debug output, maintaining a cleaner local development experience. This change provides crucial **diagnostic information** for debugging and understanding the environment in which builds are running.

This commit **enhances service resolution** by extending **framework detection** to support **file entrypoints** within the `fs-detectors` package. Previously, framework inference was limited to directory entrypoints, but now, with `framework` being an optional field, the system can correctly identify frameworks even when a specific file is designated as the `entrypoint`. This **new capability** involves adding utility functions like `inferRuntimeFromFramework` and `filterFrameworksByRuntime`, and implementing crucial **validation** in `validateServiceConfig` to prevent runtime/framework mismatches. The change improves the robustness and flexibility of service configuration, ensuring accurate framework identification and compatibility.

This commit **standardizes the auto-stripping of service route prefixes**, ensuring that all services, including those explicitly configured in `vercel.json`, consistently receive requests with their prefixes removed. Previously, this behavior was limited to zero-config services, but now the **`services-orchestrator`** in the CLI will always apply `VERCEL_SERVICE_ROUTE_PREFIX_STRIP` when a prefix is present. This **high-risk behavior change** impacts **routing for explicitly configured services**, requiring internal service routes to be defined relative to the stripped path. Multiple end-to-end test fixtures were updated to reflect this new, consistent routing behavior.

This commit **fixes a bug** in the **CLI build command**'s (`vc build`) **service route merging logic** when multiple builders return `buildOutputPath`. Previously, the command would reuse a single merged `.vercel/output/config.json`, leading to sibling service routes being dropped and incorrect app-level 404 behavior. The **bug fix** now ensures `vc build` reads each builder's own `config.json`, scopes routes to service ownership, and merges them individually per builder. This prevents route conflicts and **restores correct application routing and 404 behavior**.

This commit introduces a **fix** to the **CI/CD release workflow** to prevent unnecessary Python PyPI package releases. Previously, the default `fetch-depth` of 1 in GitHub Actions caused `HEAD^` to fail, leading `publish.mjs` to incorrectly assume a version change and trigger a release. By setting `fetch-depth: 2` in the `.github/workflows/release.yml` file, the workflow can now correctly compare the current and previous versions. This **infrastructure maintenance** improves the reliability and efficiency of the **Python PyPI release process**, ensuring releases only occur when a true version bump is detected.