@turbo/types 2.10.5-canary.4 → 2.10.5-canary.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@turbo/types",
-  "version": "2.10.5-canary.4",
+  "version": "2.10.5-canary.6",
   "description": "Turborepo types",
   "homepage": "https://turborepo.dev",
   "bugs": {

package/schemas/schema.json

@@ -301,7 +301,7 @@
           "type": "boolean"
         },
         "experimentalCargoWorkspaces": {
-          "description": "Treat the crates of a Cargo workspace as Turborepo packages.\n\nWhen enabled, Rust crates are discovered via `cargo metadata` and participate in the package graph: they resolve in `--filter` expressions, propagate `--affected`, and appear in `turbo query`. Experimental: support is landing incrementally — task execution and caching for crates are not wired up yet, so their tasks are no-ops.",
+          "description": "Treat the crates of a Cargo workspace as Turborepo packages.\n\nWhen enabled, Rust crates are discovered via `cargo metadata` and participate in the package graph: they resolve in `--filter` expressions, propagate `--affected`, and appear in `turbo query`. Entrypoint `build`, `run`, and `dev` tasks execute per crate, while verification tasks execute on the synthetic workspace package. Library crates remain graph nodes, but their tasks are no-ops because Cargo builds them through dependency closures.\n\nTask caching uses Cargo-derived inputs and caches entrypoint build deliverables. This feature is experimental.",
           "default": false,
           "type": "boolean"
         },

package/src/types/config-v2.ts

@@ -309,8 +309,13 @@ export interface FutureFlags {
    * When enabled, Rust crates are discovered via `cargo metadata` and
    * participate in the package graph: they resolve in `--filter`
    * expressions, propagate `--affected`, and appear in `turbo query`.
-   * Experimental: support is landing incrementally — task execution and
-   * caching for crates are not wired up yet, so their tasks are no-ops.
+   * Entrypoint `build`, `run`, and `dev` tasks execute per crate, while
+   * verification tasks execute on the synthetic workspace package. Library
+   * crates remain graph nodes, but their tasks are no-ops because Cargo
+   * builds them through dependency closures.
+   *
+   * Task caching uses Cargo-derived inputs and caches entrypoint build
+   * deliverables. This feature is experimental.
    *
    * @defaultValue `false`
    */