Jeff See

This commit **fixes a critical issue** where **post-build generated public files**, such as service workers, were not included in the **V3 build output** for Git-driven deployments, resulting in 404 errors. It modifies the **`@vercel/next` build process** to ensure that any files added to the `public/` directory *after* `next build` completes are correctly copied into the `.vercel/output/static/` directory. This **bug fix** ensures that all necessary static assets are properly deployed, improving the reliability of applications using dynamic public file generation and resolving 404s for these assets.

This commit delivers a crucial **bug fix** for the **backends** module, resolving a build crash that occurred when the **rolldown plugin** encountered unresolvable workspace dependencies. The issue stemmed from the plugin adding bogus paths for these dependencies to `localBuildFiles`, leading to failures in the **NFT (Next.js File Trace)** process. The fix modifies the `rolldown` plugin to correctly skip these invalid paths and also refines the `isTypeScriptFile` utility in `nft.ts` to exclude `.d.ts` files, aligning with standard TypeScript behavior. This significantly enhances **build stability** and **monorepo compatibility**, preventing crashes in projects with complex dependency structures. Comprehensive new test fixtures and assertions have been added to ensure robust coverage for workspace dependency resolution.

This commit **enhances the CI/CD pipeline's robustness** by preventing pull requests from being merged if the initial "Find Changes" GitHub Actions job fails. Previously, a failure in the `setup` job (which identifies changes) would not block PR merges because the `summary` job, responsible for merge checks, would still pass. This **configuration update** modifies the `.github/workflows/test.yml` and `.github/workflows/test-e2e.yml` files to add the `setup` job as a dependency for the `summary` job. Consequently, the **PR mergeability check** will now correctly fail if the `setup` job encounters an issue, ensuring that only thoroughly validated changes can be integrated into the codebase.

This commit performs a **dependency update**, upgrading the `@vercel/nft` package from version `1.4.0` to `1.5.0`. This **maintenance** task affects multiple **framework integration packages**, specifically `backends`, `express`, `hono`, `next`, `node`, `redwood`, and `remix`, by updating their respective `package.json` files. The update ensures these modules leverage the latest features, bug fixes, and performance improvements provided by the new `@vercel/nft` version, enhancing overall stability and functionality across the affected subsystems.

This commit performs a **dependency update** across multiple framework integration packages. It upgrades the `@vercel/nft` dependency to version `1.4.0` in `packages/backends`, `packages/express`, `packages/hono`, `packages/next`, `packages/node`, `packages/redwood`, and `packages/remix`. This **maintenance** task ensures all relevant **backend and framework integration modules** are using the latest version of the dependency. The update standardizes the `nft` version across the project, potentially bringing performance improvements or bug fixes to the build process for applications utilizing these packages.

This commit **improves the reliability and completeness of CLI evaluation result reporting** by ensuring that all evaluation outcomes, including failures, are consistently uploaded to the **centralized application**. It modifies the **`cli-evals.yml` GitHub Actions workflow** to use `if: always()` for the upload step, guaranteeing data transmission regardless of prior step success. This **maintenance** change also removes a redundant local logging step that previously only captured failures, streamlining the workflow. The primary impact is a more comprehensive and consistent view of all evaluation runs within the central app, enhancing overall visibility and debugging capabilities.

This commit **fixes** a critical issue within the **CI/CD pipeline's `ci-doctor` workflow** by correcting its trigger configuration. The `ci-doctor` previously failed to activate because it referenced incorrect workflow names (`test-e2e`, `test`) instead of the actual 'E2E Tests' and 'Unit Tests' as defined in the GitHub Actions `name:` fields. This **bug fix** updates the trigger in `.github/workflows/ci-doctor.md` and recompiles `ci-doctor.lock.yml`, ensuring the `ci-doctor` now properly monitors and reacts to failures in the **E2E and Unit Test suites**, thereby improving **CI health monitoring**. Additionally, a **new `agentics-maintenance.yml` workflow** is introduced to automate various repository cleanup tasks.

This commit **fixes** the **`ci-doctor` agentic workflow**, enabling it to trigger and execute as intended. Previously, the workflow was non-functional due to a missing compiled `.lock.yml` file and an invalid `shared/mood.md` import that blocked compilation. The invalid import was removed, and the necessary **GitHub Actions lock files** (`actions-lock.json` and `ci-doctor.lock.yml`) were generated, ensuring the workflow's dependencies are correctly specified. This **maintenance** work ensures the `ci-doctor` workflow can now properly run, improving CI health monitoring and issue detection.

This commit provides a **bug fix** for **`@vercel/build-utils`** to gracefully handle `EEXIST` errors during symlink creation, specifically in **monorepo builds using `--standalone` mode**. It modifies `packages/build-utils/src/fs/download.ts` to catch `EEXIST` errors, allowing existing symlinks with matching targets to be skipped, or replaced if their targets differ. This addresses a race condition where multiple Lambda/Edge Functions might attempt to create the same symlink, preventing build failures. The change ensures **idempotent symlink creation** and improves the **robustness and reliability of builds** for shared `node_modules` structures. New unit tests in `unit.download.test.ts` verify this behavior.

This commit **introduces documentation** for a new **CI Failure Doctor agent workflow**, designed to automatically investigate failed CI runs. It adds a new markdown file, `.github/workflows/ci-doctor.md`, which defines this **new capability** for the **CI/CD system**. Additionally, a changeset file, `.changeset/ten-islands-promise.md`, is included for versioning purposes. This work primarily involves **documentation and configuration**, with no changes to application code, enhancing the project's ability to **diagnose CI issues**.

This commit **fixes a critical routing bug** that caused dynamic **Next.js App Router API routes** (e.g., `/api/blog/posts/[id]`) to incorrectly return 404s on Vercel deployments. It modifies the **`detect-builders` module's routing logic** within `getRouteResult` to conditionally skip adding a catch-all `/api` 404 rewrite when Next.js is detected as the frontend. This **high-risk change** ensures that Next.js properly handles its own API routes, preventing erroneous 404s and improving the reliability of **Vercel's zero-config routing** for Next.js applications. New tests were added to verify correct behavior for both Next.js and non-Next.js frontends.

This commit **adds new evaluation tests** for the **`vc curl`** command within the **`packages/cli/evals`** module. Two new evaluation variants, `curl/explicit` and `curl/implicit`, are introduced to assess how an agent interacts with the command, covering both direct invocation and inferring its use from a vague prompt. This **enhances the testing capabilities** for the CLI, specifically ensuring the agent correctly invokes `vc curl` with non-interactive flags. The new evals integrate seamlessly with the existing ephemeral project setup, expanding coverage for the **CLI agent's command understanding**.

This commit introduces a **new capability** to the project's **CI/CD pipeline** by adding a step to upload evaluation results. It modifies `.github/workflows/cli-evals.yml` to include a new GitHub Actions step that leverages a newly created **Node.js script** (`packages/cli/evals/scripts/transform-agent-eval-to-canonical.js`). This script is responsible for transforming agent evaluation data and uploading it to a centralized ingest URL, thereby enabling **centralized collection and analysis of evaluation results** without affecting application code or core services. This infrastructure tooling enhances observability for agent evaluations.

This commit provides a **fix** for **public static asset handling** when deploying applications with **experimental backends**. It **enhances** the `detectBuilders` function within the **`fs-detectors` package** to correctly identify and include `@vercel/static` for projects leveraging these new runtime types. This ensures that **public files** are properly detected and served, preventing deployment issues for applications built with **experimental backends**. The **bug fix** also includes a **refactoring** of direct string comparisons to use an `isOfficialRuntime()` helper and adds **new test cases** to validate the extended functionality.

This commit introduces **new evaluation tests** and their associated **fixtures** for the `deploy` and `init` commands within the **`packages/cli/evals`** module. It adds comprehensive test files (`EVAL.ts`), prompt documentation (`PROMPT.md`), and complete fixture environments (including `package.json`, `tsconfig.json`, and source files) for both `_deploy` and `init` functionalities. This **new capability** significantly enhances the automated testing framework, ensuring the correct behavior of these critical CLI commands. Specifically, it verifies aspects like build completion and project inspection for `deploy`, and project file existence for `init`. An experiment configuration in `cli-with-skill.ts` is also updated to leverage these new evaluations.

This commit introduces **support for function configuration overrides** within the `@vercel/backends` builder, allowing external settings to dictate Node.js Lambda options during the build process. It **enhances flexibility** by spreading `functionConfigOverrides` into `NodejsLambda` constructors and exporting `NodejsLambdaOptions` from `build-utils`. Additionally, it **refactors the `fs-detectors` module** by modifying `checkUnusedFunctions` to skip validation for unused backend functions, streamlining the build pipeline. This **new capability** enables more granular control over backend deployments and resolves issues with previously flagged configurations.

This commit **re-architects the evaluation authentication system** within the **`packages/cli/evals` subsystem**, transitioning from Docker to **Vercel sandboxes**. It introduces a new mechanism to automatically provision `VERCEL_OIDC_TOKEN` for sandbox authorization, replacing the `AI_GATEWAY_API_KEY` and simplifying local setup. The change involves sourcing `VERCEL_TOKEN` from the host or environment, and hardcoding specific team/project IDs for the sandbox environment. This **high-risk infrastructure change** significantly impacts how evaluation environments are authenticated and configured, streamlining the process while introducing new credential handling.

This commit **enhances the Vercel CLI documentation** by adding comprehensive guides for deploying **Node.js backends**, **monorepos**, and applications using the **Bun runtime**. It introduces new reference markdown files (`bun.md`, `monorepos.md`, `node-backends.md`) detailing setup and usage, including examples for frameworks like Express, Hono, Elysia, Next.js, Turborepo, and Nx. The `SKILL.md` routing table is updated to link these new resources, providing users with clearer instructions and expanding the discoverability of Vercel's capabilities for these modern development patterns. This is a **documentation update** that significantly improves the user experience for developers working with these technologies.

This commit introduces a **new capability** to the **Related Projects** feature, enabling support for a **custom environment alias** in preview deployments. It adds an optional `customEnvironment` property to the `VercelRelatedProject` type within `packages/related-projects/src/types.ts`. The host resolution logic in `packages/related-projects/src/with-related-project.ts` is updated to prioritize this custom alias over the branch name, providing greater flexibility for users. This **enhancement** ensures that if a custom environment is specified, it will be used for preview host resolution. Comprehensive test cases have been added in `packages/related-projects/test/with-related-project.test.ts` to validate this new behavior.

This commit **reverts previous changes** to the **release workflow**, effectively **removing conditional guards and environment protection** from the automated release process. Specifically, it eliminates the `if: startsWith(...)` condition that gated release jobs to specific commits and removes the `environment: release` protection from the release job in `.github/workflows/release.yml`. This **maintenance** action also simplifies the summary job to always pass, removing its failure detection logic. The primary impact is the **removal of safeguards** that prevented unintended releases, increasing the risk of unapproved deployments.