Mehul Kar

This commit **refactors** the **Turborepo run cache** to improve the handling and logging of cache hit SHA context. It introduces a new helper function, `format_sha_context`, which centralizes the logic for constructing these specific messages. This helper is then integrated into the `TaskCache::write_cache_hit_status` method, ensuring that SHA context is consistently included in **verbose logging** output. The change primarily enhances the **maintainability and clarity** of the cache logging subsystem, affecting only the internal implementation of how cache hit details are presented in verbose logs.

This commit introduces the **capability to propagate Git SCM metadata** (SHA and dirty hash) to and from the **remote cache**. It modifies the `turborepo-api-client` to send `x-artifact-sha` and `x-artifact-dirty-hash` headers during artifact uploads, and updates `turborepo-cache`'s `HTTPCache` to read these headers on `exists` and `fetch` operations. This **new feature** extends previous local-only SCM metadata handling, enabling `CacheHitMetadata` to include SCM state for remote cache hits. The `turborepo-vercel-api-mock` and the OpenAPI specification are also updated to support this enhanced data, providing a more complete and traceable caching experience.

This commit introduces a **new capability** to **Turborepo's caching and reporting system** by **surfacing SCM metadata** in the **Run Summary JSON output**. It extends the `CacheHitMetadata` and `HashTrackerCacheHitMetadata` structs to carry the Git commit `sha` and `dirtyHash` from cache sidecar files. Consequently, upon a cache hit, the `.turbo/runs/*.json` summary will now include these fields within the `cache` object. This **enhancement** allows consumers to **trace the exact commit that produced a cached artifact**, significantly improving the **observability and traceability** of build results.

This commit introduces a **new capability** to the **Turborepo caching mechanism** by storing the current Git HEAD SHA and a hash of uncommitted working-tree changes (`dirty_hash`) within each cache entry's metadata. This enhancement, primarily affecting the `turborepo-cache` and `turborepo-lib` modules, allows for precise identification of the source code state that produced a cached artifact. The `turborepo-scm` module gains new logic to compute this dirty hash. This enables powerful reverse lookups, significantly improving reproducibility and debugging by linking cache hits directly to specific commits and their uncommitted modifications. The new metadata fields are optional, ensuring **backward compatibility** with existing cache entries.

This commit **fixes a bug** in the **CLI's deployment command** where `vc deploy --json` produced invalid JSON output when piped, due to an extraneous deployment URL being written to `stdout` alongside the intended JSON. A new `jsonOutput` flag was introduced and propagated through `CreateOptions` to the `processDeployment` utility, which now **conditionally suppresses the bare URL output** when JSON output is requested. This ensures **valid JSON output** for programmatic consumption of deployment information. A **new unit test** was added to verify that only valid JSON is emitted when `--json` is used and `stdout` is not a TTY.

This commit introduces a **new capability** to the **Vercel CLI's `deploy` command**, enabling users to retrieve deployment details in a machine-readable **JSON format**. By adding the `--json` or `--format=json` flags to `vc deploy`, the command will now output essential information such as `id`, `url`, `inspectorUrl`, and `deploymentApiUrl` to stdout. This enhancement primarily affects the **`cli` package** and its **`deploy` subcommand**, providing a standardized output for scripting and automation, and includes corresponding **telemetry tracking** and **unit tests**.

This commit **improves the debuggability of test logs** by **removing the custom `logWithinTest` wrapper function** and directly utilizing `console.log` within the **deployment testing utilities**. The previous wrapper obscured stack traces, making it challenging to pinpoint the origin of log messages during test execution. This **test infrastructure improvement** affects functions such as `nowDeploy` and `testDeployment` in `test/lib/deployment/now-deploy.js` and `test/lib/deployment/test-deployment.js`. By ensuring stack traces correctly reflect the call site, this **maintenance and refactoring** change significantly enhances the clarity and ease of debugging for **deployment-related tests**.

This commit **fixes broken unit tests** within the **CLI package** by adjusting the `waitForPrompt` utility. The default timeout for the `waitForPrompt` function in `packages/cli/test/helpers/wait-for-prompt.ts` has been increased from 3000ms to 5000ms. This **maintenance change** resolves recent test failures on the `main` branch, ensuring the stability and reliability of the CLI's test suite.

This commit **refactors the test suite** for the **import builders** to improve maintainability and enforce encapsulation. It modifies the tests to **stop directly unit testing the private `resolveBuilders` function**, instead relying on public APIs and mocking the installation process. This **chore** ensures that internal implementation details, like `resolveBuilders`, are no longer exposed or directly tested, making the test suite more resilient to future refactors. Furthermore, it reinforces the private nature of `resolveBuilders` by **stopping its export**, preventing external dependencies on an internal component.

This commit performs a **refactoring** within the **CLI's builder installation logic** to improve its internal architecture and simplify its API. It makes the `untracedInstallBuilders` function **module-private**, ensuring that tracing concerns are encapsulated within the primary `installBuilders` function. The `installBuilders` function now accepts an optional `span` parameter, allowing it to internally manage both traced and untraced code paths. This change **streamlines the `installBuilders` interface**, preventing callers from needing to explicitly choose between traced and untraced variants.

This commit implements a **telemetry improvement** for the **CLI** by **renaming `vc.builder` span attributes** to ensure proper Datadog integration. Specifically, it prefixes `name`, `version`, and `dynamicallyInstalled` attributes with `builder.` (e.g., `builder.name`). This **compatibility fix** prevents conflicts with Datadog's reserved `version` tag, ensuring **accurate and non-conflicting telemetry data** is reported for builder-related operations. The change enhances **observability** by providing correctly categorized metrics within Datadog.

This commit significantly enhances the **observability** of the **builder installation process** by introducing a new `tracedInstallBuilders` function. It wraps the installation logic with a `vc.installBuilders` span, adding crucial `packages` and `error` tags to provide detailed tracing information, especially for debugging failures. The related `installBuilders` and `tracedInstallBuilders` functions were **refactored** into a new `install-builders.ts` file for improved code organization. This **instrumentation** allows the **build command** to pass a tracing span through `importBuilders`, enabling comprehensive monitoring of builder setup.

This commit **reconfigures the `cli` package** by moving **builder packages back into its direct dependencies**, effectively reversing a recent architectural change. It updates `packages/cli/package.json` to include builders as `dependencies` rather than `peerDependencies`, ensuring they are bundled with the **CLI**. This change impacts the **CLI's dependency resolution and distribution**, simplifying how it consumes and manages various framework and runtime builders. Furthermore, deployment timestamps for all builder packages were updated to invalidate caches and trigger comprehensive **e2e test validation**.

This commit **fixes a bug** in the **CLI's builder import resolution strategy**, ensuring that the CLI first checks its own `node_modules` for a builder before attempting to install it if not found in the local cache. This change improves performance in environments like the Vercel build container, which pre-install builders. Additionally, it **resolves a failing E2E test** for the `eleventy-v0` fixture by preventing Eleventy from attempting to process the contents of the `.vercel/builders` directory, which was incidentally created by the previous incorrect resolution logic. The fix streamlines builder discovery and prevents unnecessary installations.

This commit performs **maintenance** by **removing the `release-canary` GitHub Actions workflow**, thereby streamlining the project's **CI/CD pipeline** and simplifying its release process. The change also updates the `AGENTS.md` documentation to reflect this removal and clarify internal changeset rules. This action primarily impacts the **build and release infrastructure**, ensuring a cleaner and more focused continuous integration setup by eliminating an unused workflow.

This commit **refactors the `vercel` CLI's dependency management** by moving builder packages from direct `dependencies` to `peerDependencies` and marking them as optional. This change prevents builders from being bundled directly into the CLI, significantly **reducing its published size**. A **new capability** is introduced to **dynamically resolve and install these builders at runtime** from the registry, caching them locally in `.vercel/builders` for efficient on-demand usage. This impacts the **`packages/cli` module**, **CI/CD test workflows**, and **Vitest configuration**, ensuring the CLI remains functional while optimizing its distribution and resource footprint.

This commit **enhances observability** within the **CLI's builder resolution logic** by introducing a debug log. This new log will display resolved builder versions, aiding in the diagnosis of issues, particularly for frameworks like `11ty`. It also includes minor **maintenance updates**, such as adding JSDoc comments to the `BuilderWithPkg` interface and a description to the `static-build` package.json. This **low-risk change** primarily focuses on **improving debugging capabilities** without altering any core logic or security aspects.

This commit **reverts** a prior change that restructured the dependencies of the **`@vercel/cli` package**. As a **maintenance** action, it moves `@vercel/backends` back from `peerDependencies` to `dependencies` and reverses the move of other packages between `dependencies` and `peerDependencies`, also removing the `peerDependenciesMeta` section. This ensures the **CLI's core dependencies** are directly managed, potentially resolving installation or compatibility issues introduced by the previous peer dependency model.

This commit performs a **maintenance chore** by **removing debug output** from the **CLI output manager**. It specifically modifies `packages/cli/src/output-manager.ts` to disable verbose logging by setting an internal debug flag to `false`. This change ensures that users of the **CLI** will no longer encounter unnecessary debug messages, leading to a cleaner and less cluttered console experience. The overall impact is an improvement in the user-facing output of the **CLI**.

This commit **refactors** the `vercel` **CLI**'s dependency management by moving **builder packages** from direct `dependencies` to `peerDependencies` in `packages/cli/package.json`, marking them as optional to prevent bundling. This change significantly **reduces the published CLI bundle size** and improves installation efficiency. To maintain functionality, a **new capability** is introduced in the `resolveBuilders` function, enabling **on-demand installation** of the correct builder versions at runtime from the registry, which are then cached locally in `.vercel/builders`. This impacts the `vercel` **CLI**'s dependency resolution and required updates to CI/CD workflows to build these peer dependencies during testing.