@turbo/types 2.10.6-canary.2 → 2.10.6-canary.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@turbo/types",
-  "version": "2.10.6-canary.2",
+  "version": "2.10.6-canary.4",
   "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`. 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\nEntrypoints implicitly register `build`; crates with one binary also register `run` and `dev`. The workspace package registers `test`, `check`, `clippy`/`lint`, `bench`, and `doc`/`docs`. Normal task definitions configure or override these defaults, and package configuration can exclude them with `extends: false`.\n\nTask caching uses Cargo-derived inputs and caches entrypoint build deliverables. This feature is experimental.",
+          "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`. Filtered builds execute each selected crate. Unfiltered builds prefer entrypoints, falling back to libraries when no entrypoints exist. Entrypoints also expose `run` and `dev`. The `test`, `check`, `clippy`/`lint`, `bench`, and `doc`/`docs` tasks are selectable per crate with `--filter`. An unfiltered run executes one workspace-wide Cargo verification command; filtered runs use the selected crates, or the workspace command when the workspace package is selected directly.\n\nAll crates implicitly register `build` and the verification tasks; entrypoints with one binary also register `run` and `dev`. The workspace package registers the verification tasks. Normal task definitions configure or override these defaults, and package configuration can exclude them with `extends: false`.\n\nTask caching uses Cargo-derived inputs and caches entrypoint build deliverables. Library builds default to uncached. This feature is experimental.",
           "default": false,
           "type": "boolean"
         },

package/src/types/config-v2.ts

@@ -309,19 +309,23 @@ 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`.
-   * 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.
-   *
-   * Entrypoints implicitly register `build`; crates with one binary also
-   * register `run` and `dev`. The workspace package registers `test`,
-   * `check`, `clippy`/`lint`, `bench`, and `doc`/`docs`. Normal task
-   * definitions configure or override these defaults, and package
-   * configuration can exclude them with `extends: false`.
+   * Filtered builds execute each selected crate. Unfiltered builds prefer
+   * entrypoints, falling back to libraries when no entrypoints exist.
+   * Entrypoints also expose `run` and `dev`. The `test`, `check`, `clippy`/`lint`, `bench`, and
+   * `doc`/`docs` tasks are selectable per crate with `--filter`. An
+   * unfiltered run executes one workspace-wide Cargo verification command;
+   * filtered runs use the selected crates, or the workspace command when the
+   * workspace package is selected directly.
+   *
+   * All crates implicitly register `build` and the verification tasks;
+   * entrypoints with one binary also register `run` and `dev`. The workspace
+   * package registers the verification tasks. Normal task definitions
+   * configure or override these defaults, and package configuration can
+   * exclude them with `extends: false`.
    *
    * Task caching uses Cargo-derived inputs and caches entrypoint build
-   * deliverables. This feature is experimental.
+   * deliverables. Library builds default to uncached. This feature is
+   * experimental.
    *
    * @defaultValue `false`
    */