turbo 2.11.7 → 2.11.8-canary.2

package/docs/reference/configuration.mdx

@@ -304,9 +304,8 @@ Enable experimental features that will become the default behavior in future ver
 </Callout>
 
 <Callout type="warn">
-  Changing any future flag will affect the [global
-  hash](/docs/crafting-your-repository/caching#global-hash-inputs), causing all
-  tasks to miss cache on the next run.
+  Future flags that change behavior can invalidate the [task
+  cache](/docs/crafting-your-repository/caching).
 </Callout>
 
 #### `errorsOnlyShowHash`
@@ -458,9 +457,9 @@ With this configuration, running `turbo prune frontend` will include `tsconfig.j
 
 Default: `false`
 
-Resolve [`--filter`](/docs/reference/run#--filter-string) at the **task level** instead of the **package level**. Git-range filters (e.g. `--filter=[main]`) match changed files against each task's [`inputs`](#inputs) globs, and the `...` dependency/dependent syntax traverses the Task Graph in addition to the Package Graph.
+Resolve [`--filter`](/docs/reference/run#--filter-string) at the **task level** instead of the **package level**. Git-range filters (e.g. `--filter=[main]`) match changed files against each task's [`inputs`](#inputs) globs, and the `...` dependency/dependent syntax traverses the Task Graph instead of the Package Graph.
 
-Without this flag, `--filter` operates on the Package Graph: a git-range selector marks entire packages as matched if any file in the package changed, and `...` follows package-level dependencies. With this flag, resolution moves to the Task Graph: only tasks whose `inputs` actually match the changed files are selected, and `...` follows task-level dependencies (e.g. `web#build -> schema#gen` is traversed even if `web` has no package-level dependency on `schema`).
+Without this flag, `--filter` operates on the Package Graph: a git-range selector marks entire packages as matched if any file in the package changed, and `...` follows package-level dependencies. With this flag, resolution moves to the Task Graph: only tasks whose `inputs` actually match the changed files are selected, and `...` follows task-level dependencies (e.g. `web#build -> schema#gen` is traversed even if `web` has no package-level dependency on `schema`). Package dependencies alone do not cause tasks in dependency packages to be selected.
 
 ```jsonc title="./turbo.json"
 {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "turbo",
-  "version": "2.11.7",
+  "version": "2.11.8-canary.2",
   "description": "Turborepo is the build system for coding agents.",
   "homepage": "https://turborepo.dev",
   "bugs": "https://github.com/vercel/turborepo/issues",
@@ -19,12 +19,12 @@
   ],
   "main": "./bin/turbo",
   "optionalDependencies": {
-    "@turbo/darwin-64": "2.11.7",
-    "@turbo/darwin-arm64": "2.11.7",
-    "@turbo/linux-64": "2.11.7",
-    "@turbo/linux-arm64": "2.11.7",
-    "@turbo/windows-64": "2.11.7",
-    "@turbo/windows-arm64": "2.11.7"
+    "@turbo/darwin-64": "2.11.8-canary.2",
+    "@turbo/darwin-arm64": "2.11.8-canary.2",
+    "@turbo/linux-64": "2.11.8-canary.2",
+    "@turbo/linux-arm64": "2.11.8-canary.2",
+    "@turbo/windows-64": "2.11.8-canary.2",
+    "@turbo/windows-arm64": "2.11.8-canary.2"
   },
   "scripts": {
     "postversion": "node bump-version.js"

package/schema.json

@@ -331,6 +331,11 @@
           "default": false,
           "type": "boolean"
         },
+        "experimentalSetup": {
+          "description": "Opt into experimental setup features that are still in progress.\n\nSetup invocation requires this flag; help is available without it. The `turbo.lock` format is unstable. Only parsing and help are implemented; provisioning, planning, and checking return a diagnostic. Setup does not interpret `turbo.lock` or change run or hash behavior.",
+          "default": false,
+          "type": "boolean"
+        },
         "filterUsingTasks": {
           "description": "Resolve `--filter` at the task level instead of the package level. Git-range filters (e.g. `--filter=[main]`) will match against task `inputs` globs, and the `...` dependency/dependent syntax will traverse the task graph in addition to the package graph.",
           "default": false,