turbo 2.11.10 → 2.11.11-canary.2

package/bin/turbo

@@ -537,9 +537,18 @@ function runTurboChild(env, useCtrlCPipe) {
     }
   };
 
+  const handleSighup = () => {
+    if (!child.killed) {
+      child.kill("SIGHUP");
+    }
+  };
+
   const cleanup = () => {
     process.off("SIGINT", handleSigint);
     process.off("SIGTERM", handleSigterm);
+    if (process.platform !== "win32") {
+      process.off("SIGHUP", handleSighup);
+    }
     process.stdin.off("data", handleInput);
     restoreStdin();
     ctrlCPipe?.destroy();
@@ -547,6 +556,9 @@ function runTurboChild(env, useCtrlCPipe) {
 
   process.on("SIGINT", handleSigint);
   process.on("SIGTERM", handleSigterm);
+  if (process.platform !== "win32") {
+    process.on("SIGHUP", handleSighup);
+  }
 
   child.once("error", (error) => {
     cleanup();

package/docs/crafting-your-repository/constructing-ci.mdx

@@ -93,7 +93,7 @@ As your codebase and CI grow, you may start to look for more ways to get even fa
 <Step>
 ### Checkout the repository
 
-Start by cloning your repository. A clone with sufficient history is necessary for comparisons — if the checkout is too shallow, all packages will be considered changed. For example, cloning with `--filter=blob:none --depth=0` will ensure the right history is available.
+Start by cloning your repository. A clone with sufficient history is necessary for comparisons — if the checkout is too shallow, all packages will be considered changed. For example, a blobless clone with full history (`git clone --filter=blob:none`, without `--depth`) gives the comparison the history it needs. With `actions/checkout`, set `filter: blob:none` and `fetch-depth: 0`.
 
 By default, `turbo query affected` compares against the merge-base with your default branch.
 

package/docs/guides/ci-vendors/vercel.mdx

@@ -1,9 +1,9 @@
 ---
 title: Vercel
-description: Learn how to use Turborepo on Vercel.
+description: Learn how to deploy your Turborepo and run tasks with Vercel CI.
 product: turborepo
 type: integration
-summary: Deploy your Turborepo on Vercel with zero-config Remote Caching.
+summary: Deploy your Turborepo on Vercel and run tasks with Vercel CI using zero-config Remote Caching.
 prerequisites:
   - /docs/guides/ci-vendors
 related:
@@ -19,6 +19,12 @@ To deploy your Turborepo on Vercel, [create a new project](https://vercel.com/ne
 
 For more information about deploying your Turborepo to Vercel, [visit the Vercel documentation](https://vercel.com/docs/monorepos/turborepo).
 
+## Vercel CI
+
+[Vercel CI](https://vercel.com/docs/ci) runs your Turborepo tasks, such as tests, linting, and type checks, when you push code. It uses your Task Graph to run tasks in dependency order, skips unaffected tasks, and reuses cached results with zero-config Vercel Remote Cache. Each task runs in its own isolated compute instance.
+
+To get started, follow the [Vercel CI setup instructions](https://vercel.com/docs/ci) to enable CI for your repository and select which tasks to run. For more details, see the [configuration reference](https://vercel.com/docs/ci/configuration) for task dependencies and resource sizing, and the [environment variables guide](https://vercel.com/docs/ci/environment-variables) for secrets and other values your tasks need.
+
 ## Filtered installs
 
 You can speed up installs by only installing the dependencies for the application being deployed and its Workspace dependencies. Set a custom Install Command in the application's `vercel.json` or [in your project's Build and Deployment settings](https://vercel.com/d?to=%2F%5Bteam%5D%2F%5Bproject%5D%2Fsettings%2Fbuild-and-deployment%23framework-settings&title=Build+and+Deployment+settings):

package/docs/guides/skipping-tasks.mdx

@@ -26,7 +26,7 @@ Ideally, you would do a quick check to see if any of that work needs to happen i
   checkout. If the checkout is too shallow, then all packages will be considered
   changed.
 
-For example, setting up Git to check out with `--filter=blob:none --depth=0` will ensure `turbo query affected` has the right history to work correctly.
+For example, a blobless clone with full history (`git clone --filter=blob:none`, without `--depth`) gives `turbo query affected` the history it needs. With `actions/checkout`, set `filter: blob:none` and `fetch-depth: 0`.
 
 </Callout>
 

package/docs/guides/tools/prisma.mdx

@@ -13,7 +13,7 @@ import { CreateTurboCallout } from "./create-turbo-callout.tsx";
 
 [Prisma](https://www.prisma.io/) unlocks a new level of developer experience when working with databases thanks to its intuitive data model, automated migrations, type-safety & auto-completion.
 
-[Their official guide](https://www.prisma.io/docs/guides/turborepo) describes how to integrate Prisma into a Turborepo, including:
+[Their official guide](https://www.prisma.io/docs/guides/deployment/turborepo) describes how to integrate Prisma into a Turborepo, including:
 
 - Prisma client initialization
 - Packaging the client as an [Internal Package](/docs/core-concepts/internal-packages)

package/docs/guides/tools/shadcn-ui.mdx

@@ -18,7 +18,7 @@ To get started with shadcn/ui in a new monorepo, run:
 <Tab value="pnpm">
 
 ```bash title="Terminal"
-pnpm dlx shadcn@canary init
+pnpm dlx shadcn@latest init
 ```
 
 </Tab>
@@ -26,7 +26,7 @@ pnpm dlx shadcn@canary init
 <Tab value="yarn">
 
 ```bash title="Terminal"
-npx shadcn@canary init
+npx shadcn@latest init
 ```
 
 </Tab>
@@ -34,7 +34,7 @@ npx shadcn@canary init
 <Tab value="npm">
 
 ```bash title="Terminal"
-npx shadcn@canary init
+npx shadcn@latest init
 ```
 
 </Tab>
@@ -42,7 +42,7 @@ npx shadcn@canary init
 <Tab value="bun">
 
 ```bash title="Terminal"
-bunx shadcn@canary init
+bunx shadcn@latest init
 ```
 
 </Tab>
@@ -50,7 +50,7 @@ bunx shadcn@canary init
 <Tab value="nub">
 
 ```bash title="Terminal"
-nubx shadcn@canary init
+nubx shadcn@latest init
 ```
 
 </Tab>
@@ -58,7 +58,7 @@ nubx shadcn@canary init
 <Tab value="aube">
 
 ```bash title="Terminal"
-aubx shadcn@canary init
+aubx shadcn@latest init
 ```
 
 </Tab>
@@ -74,7 +74,7 @@ To add a component, run:
 <Tab value="pnpm">
 
 ```bash title="Terminal"
-pnpm dlx shadcn@canary add [COMPONENT]
+pnpm dlx shadcn@latest add [COMPONENT]
 ```
 
 </Tab>
@@ -82,7 +82,7 @@ pnpm dlx shadcn@canary add [COMPONENT]
 <Tab value="yarn">
 
 ```bash title="Terminal"
-npx shadcn@canary add [COMPONENT]
+npx shadcn@latest add [COMPONENT]
 ```
 
 </Tab>
@@ -90,7 +90,7 @@ npx shadcn@canary add [COMPONENT]
 <Tab value="npm">
 
 ```bash title="Terminal"
-npx shadcn@canary add [COMPONENT]
+npx shadcn@latest add [COMPONENT]
 ```
 
 </Tab>
@@ -98,7 +98,7 @@ npx shadcn@canary add [COMPONENT]
 <Tab value="bun">
 
 ```bash title="Terminal"
-bunx shadcn@canary add [COMPONENT]
+bunx shadcn@latest add [COMPONENT]
 ```
 
 </Tab>
@@ -106,7 +106,7 @@ bunx shadcn@canary add [COMPONENT]
 <Tab value="nub">
 
 ```bash title="Terminal"
-nubx shadcn@canary add [COMPONENT]
+nubx shadcn@latest add [COMPONENT]
 ```
 
 </Tab>
@@ -114,7 +114,7 @@ nubx shadcn@canary add [COMPONENT]
 <Tab value="aube">
 
 ```bash title="Terminal"
-aubx shadcn@canary add [COMPONENT]
+aubx shadcn@latest add [COMPONENT]
 ```
 
 </Tab>

package/docs/reference/configuration.mdx

@@ -308,6 +308,24 @@ Enable experimental features that will become the default behavior in future ver
   cache](/docs/crafting-your-repository/caching).
 </Callout>
 
+#### `hashFilePermissions`
+
+Default: `false`
+
+Include executable permissions in file hashes for task inputs and global dependencies. With this flag enabled, changing an input file from non-executable to executable, or back, changes the task hash even when its contents stay the same.
+
+On Unix, a regular file is executable if any owner, group, or other executable bit is set. On Windows, regular files are treated as non-executable. Symlink permissions and read or write permission bits do not affect hashes.
+
+Enabling this flag changes all task hashes. Existing cache entries are not reused. With the flag disabled, Turborepo preserves content-only file hashing.
+
+```jsonc title="./turbo.json"
+{
+  "futureFlags": {
+    "hashFilePermissions": true,
+  },
+}
+```
+
 #### `errorsOnlyShowHash`
 
 Default: `false`

package/docs/reference/query.mdx

@@ -241,7 +241,7 @@ turbo query affected [flags]
   checkout. If the checkout is too shallow, then all packages will be considered
   changed.
 
-For example, setting up Git to check out with `--filter=blob:none --depth=0` will ensure `turbo query affected` has the right history to work correctly.
+For example, a blobless clone with full history (`git clone --filter=blob:none`, without `--depth`) gives `turbo query affected` the history it needs. With `actions/checkout`, set `filter: blob:none` and `fetch-depth: 0`.
 
 </Callout>
 

package/docs/reference/run.mdx

@@ -69,7 +69,7 @@ By default, the flag is equivalent to `--filter=...[main...HEAD]`. This consider
   checkout. If the checkout is too shallow, then all packages will be considered
   changed.
 
-For example, setting up Git to check out with `--filter=blob:none --depth=0` will ensure `--affected` has the right history to work correctly.
+For example, a blobless clone with full history (`git clone --filter=blob:none`, without `--depth`) gives `--affected` the history it needs. With `actions/checkout`, set `filter: blob:none` and `fetch-depth: 0`.
 
 </Callout>
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "turbo",
-  "version": "2.11.10",
+  "version": "2.11.11-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.10",
-    "@turbo/darwin-arm64": "2.11.10",
-    "@turbo/linux-64": "2.11.10",
-    "@turbo/linux-arm64": "2.11.10",
-    "@turbo/windows-64": "2.11.10",
-    "@turbo/windows-arm64": "2.11.10"
+    "@turbo/darwin-64": "2.11.11-canary.2",
+    "@turbo/darwin-arm64": "2.11.11-canary.2",
+    "@turbo/linux-64": "2.11.11-canary.2",
+    "@turbo/linux-arm64": "2.11.11-canary.2",
+    "@turbo/windows-64": "2.11.11-canary.2",
+    "@turbo/windows-arm64": "2.11.11-canary.2"
   },
   "scripts": {
     "postversion": "node bump-version.js"

package/schema.json

@@ -444,6 +444,11 @@
           "default": false,
           "type": "boolean"
         },
+        "hashFilePermissions": {
+          "description": "Include file executable permissions in task hashes. Disabled by default. Enabling this flag changes all task hashes. On Unix, any executable bit marks a regular file as executable. On Windows, files are non-executable. Symlink permissions and other permission bits do not affect hashes.",
+          "default": false,
+          "type": "boolean"
+        },
         "longerSignatureKey": {
           "description": "Enforce a minimum length of 32 bytes for `TURBO_REMOTE_CACHE_SIGNATURE_KEY` when `remoteCache.signature` is enabled. Short keys weaken the HMAC-SHA256 signature, making brute-force tag collision feasible.",
           "default": false,
@@ -1155,9 +1160,9 @@
       ]
     },
     "ToolPolicy": {
-      "description": "How `turbo setup` prepares a toolchain's tools. `managed` provisions the locked version for this repository. `verify-system` uses an installed tool after verifying that it matches the locked version. `skip` neither provisions nor verifies the tool, which also skips the toolchain's dependencies.",
+      "description": "How `turbo setup` prepares a toolchain's tools. `managed` provisions the locked version for this repository. `skip` neither provisions nor verifies the tool, which also skips the toolchain's dependencies.",
       "type": "string",
-      "enum": ["managed", "verify-system", "skip"]
+      "enum": ["managed", "skip"]
     },
     "ToolchainSetupPolicy": {
       "description": "Setup policy for one toolchain. Omitted values use the root `setup` values, then the inferred default.",