@turbo/types 2.10.6-canary.1 → 2.10.6-canary.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/schemas/schema.json +1 -1
- package/src/types/config-v2.ts +6 -0
package/package.json
CHANGED
package/schemas/schema.json
CHANGED
|
@@ -301,7 +301,7 @@
|
|
|
301
301
|
"type": "boolean"
|
|
302
302
|
},
|
|
303
303
|
"experimentalCargoWorkspaces": {
|
|
304
|
-
"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.",
|
|
304
|
+
"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.",
|
|
305
305
|
"default": false,
|
|
306
306
|
"type": "boolean"
|
|
307
307
|
},
|
package/src/types/config-v2.ts
CHANGED
|
@@ -314,6 +314,12 @@ export interface FutureFlags {
|
|
|
314
314
|
* crates remain graph nodes, but their tasks are no-ops because Cargo
|
|
315
315
|
* builds them through dependency closures.
|
|
316
316
|
*
|
|
317
|
+
* Entrypoints implicitly register `build`; crates with one binary also
|
|
318
|
+
* register `run` and `dev`. The workspace package registers `test`,
|
|
319
|
+
* `check`, `clippy`/`lint`, `bench`, and `doc`/`docs`. Normal task
|
|
320
|
+
* definitions configure or override these defaults, and package
|
|
321
|
+
* configuration can exclude them with `extends: false`.
|
|
322
|
+
*
|
|
317
323
|
* Task caching uses Cargo-derived inputs and caches entrypoint build
|
|
318
324
|
* deliverables. This feature is experimental.
|
|
319
325
|
*
|