turbo 2.11.5 → 2.11.7

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

@@ -181,7 +181,29 @@ Using global `turbo` is convenient in CI workflows, allowing you to easily run c
 
 However, in some cases, you may be running `turbo` commands or scripts that use `turbo` **before installing packages with your package manager**. One example of this is [using `turbo prune` to create a Docker image](/docs/guides/tools/docker#example). In this situation, global `turbo` will not be able to use the version from `package.json` because the binary for that version hasn't been installed yet.
 
-For this reason, we encourage you to **pin your global installation of `turbo` in CI to the major version in `package.json`** since breaking changes will not be introduced within a major version. You could additionally opt for added stability by pinning an exact version, trading off for maintenance burden to receive bug fixes in patch releases.
+For CI steps before dependencies are installed, pin the standalone binary to an exact version compatible with your repository's `turbo` dependency. Set `TURBO_VERSION` when running the [installer](/docs/getting-started/installation#global-installation):
+
+<Tabs items={["macOS and Linux", "Windows x64"]}>
+  <Tab value="macOS and Linux">
+
+```sh title="Terminal"
+curl -fsSL https://turborepo.dev/install | TURBO_VERSION=2.11.5 sh
+```
+
+  </Tab>
+  <Tab value="Windows x64">
+
+```powershell title="PowerShell"
+$env:TURBO_VERSION = '2.11.5'
+irm https://turborepo.dev/install.ps1 | iex
+```
+
+  </Tab>
+</Tabs>
+
+<Callout type="info">
+  Standalone releases start at 2.11.5. To use an older version, install it with your package manager instead.
+</Callout>
 
 ### Use `turbo run` in CI
 

package/docs/getting-started/add-to-existing-repository.mdx

@@ -46,16 +46,36 @@ familiar with Turborepo.
 <Step>
 ### Install `turbo`
 
-We recommend you install `turbo` both globally and into your repository's root for the best developer experience.
+Install `turbo` globally.
+
+<Tabs items={["macOS and Linux", "Windows x64"]}>
+  <Tab value="macOS and Linux">
+
+```sh title="Terminal"
+curl -fsSL https://turborepo.dev/install | sh
+```
+
+  </Tab>
+  <Tab value="Windows x64">
+
+```powershell title="PowerShell"
+irm https://turborepo.dev/install.ps1 | iex
+```
+
+  </Tab>
+</Tabs>
+
+<Callout type="info">
+  The binaries are also available in the [GitHub release assets](https://github.com/vercel/turborepo/releases).
+</Callout>
+
+Then pin `turbo` in your repository's root:
 
 <PackageManagerTabs>
   <Tab value="pnpm">
       Ensure you have created a `pnpm-workspace.yaml` file before you begin the installation. Failure to have this file will result in an error that says: ` --workspace-root may only be used inside a workspace`.
 
     ```bash title="Terminal"
-    # Global install
-    pnpm add turbo --global
-    # Install in repository
     pnpm add turbo --save-dev --workspace-root
     ```
 
@@ -63,9 +83,6 @@ We recommend you install `turbo` both globally and into your repository's root f
   <Tab value="yarn">
 
     ```bash title="Terminal"
-    # Global install
-    yarn global add turbo
-    # Install in repository
     yarn add turbo --dev
     ```
 
@@ -73,9 +90,6 @@ We recommend you install `turbo` both globally and into your repository's root f
   <Tab value="npm">
 
     ```bash title="Terminal"
-    # Global install
-    npm install turbo --global
-    # Install in repository
     npm install turbo --save-dev
     ```
 
@@ -83,9 +97,6 @@ We recommend you install `turbo` both globally and into your repository's root f
   <Tab value="bun">
 
     ```bash title="Terminal"
-    # Global install
-    bun install turbo --global
-    # Install in repository
     bun install turbo --dev
     ```
 
@@ -94,9 +105,6 @@ We recommend you install `turbo` both globally and into your repository's root f
 <Tab value="nub">
 
     ```bash title="Terminal"
-    # Global install
-    nub add turbo --global
-    # Install in repository
     nub add turbo --save-dev
     ```
 
@@ -105,9 +113,6 @@ We recommend you install `turbo` both globally and into your repository's root f
 <Tab value="aube">
 
     ```bash title="Terminal"
-    # Global install
-    aube add turbo --global
-    # Install in repository
     aube add turbo --save-dev
     ```
 
@@ -115,7 +120,7 @@ We recommend you install `turbo` both globally and into your repository's root f
 
 </PackageManagerTabs>
 
-To learn more about why we recommend both installations, visit the [Installation page](/docs/getting-started/installation).
+The installed local version takes precedence when you run the global binary in your repository. See [Installation](/docs/getting-started/installation#repository-installation) for details.
 
 </Step>
 <Step>

package/docs/getting-started/index.mdx

@@ -16,30 +16,7 @@ If you're new to Turborepo, you can follow these steps to get started.
 <Step>
 ## Install Turborepo
 
-Install `turbo` globally so you can conveniently run `turbo` commands in your terminal from anywhere in your repository.
-
-<Tabs items={["npm", "yarn", "pnpm"]} storageKey="selected-pkg-manager">
-  <Tab value="npm">
-  ```bash title="Terminal"
-  npm install turbo --global
-  ```
-
-  </Tab>
-  <Tab value="yarn">
-  ```bash title="Terminal"
-  yarn global add turbo
-  ```
-
-  </Tab>
-  <Tab value="pnpm">
-  ```bash title="Terminal"
-  pnpm add turbo --global
-  ```
-
-  </Tab>
-</Tabs>
-
-To learn more about installing `turbo`, see the [installation guide](/docs/getting-started/installation).
+Install the standalone `turbo` binary to run commands from your terminal. See the [installation guide](/docs/getting-started/installation#global-installation) for supported platforms and instructions.
 
 </Step>
 <Step>

package/docs/getting-started/installation.mdx

@@ -3,7 +3,7 @@ title: Installation
 description: Learn how to get started with Turborepo.
 product: turborepo
 type: guide
-summary: Install Turborepo globally and in your repository using your preferred package manager.
+summary: Install Turborepo globally and in your repository.
 prerequisites:
   - /docs/getting-started
 related:
@@ -69,60 +69,38 @@ For more details on the starter, [visit the README for the basic starter on GitH
 
 ## Installing `turbo`
 
-`turbo` can be installed both globally **and** in your repository. We highly recommend installing both ways so you can take advantage of fast, convenient workflows _and_ a stable version of `turbo` for all developers working in your repository.
+You can install `turbo` globally and pin a version in your repository. When a local binary is installed, the global binary defers to it.
 
 ### Global installation
 
 A global install of `turbo` brings flexibility and speed to your local workflows.
 
-<PackageManagerTabs>
-
-  <Tab value="pnpm">
-  ```bash title="Terminal"
-  pnpm add turbo --global
-  ```
-
-  </Tab>
-
-  <Tab value="yarn">
-  ```bash title="Terminal"
-  yarn global add turbo
-  ```
+<Tabs items={["macOS and Linux", "Windows x64"]}>
+  <Tab value="macOS and Linux">
 
-  </Tab>
-
-  <Tab value="npm">
-  ```bash title="Terminal"
-  npm install turbo --global
-  ```
-
-  </Tab>
-
-  <Tab value="bun">
-  ```bash title="Terminal"
-  bun install turbo --global
-  ```
+```sh title="Terminal"
+curl -fsSL https://turborepo.dev/install | sh
+```
 
   </Tab>
+  <Tab value="Windows x64">
 
-
-<Tab value="nub">
-  ```bash title="Terminal"
-  nub add turbo --global
-  ```
+```powershell title="PowerShell"
+irm https://turborepo.dev/install.ps1 | iex
+```
 
   </Tab>
+</Tabs>
 
-<Tab value="aube">
-  ```bash title="Terminal"
-  aube add turbo --global
-  ```
-
-  </Tab>
+<Callout type="info">
+  See the [support policy](/docs/support-policy#platforms) for supported platforms.
+</Callout>
 
-</PackageManagerTabs>
+<Callout type="info">
+  The binaries are also available directly in the [GitHub release assets](https://github.com/vercel/turborepo/releases), starting with 2.11.5. To install an older version, use your package manager.
+</Callout>
 
-Once installed globally, you can run your scripts through `turbo` from your terminal, quickly running one-off commands to use within your repository. For example:
+After installing `turbo`, you can run commands from your terminal. For example:
 
 - `turbo build`: Run `build` scripts following your repository's dependency graph
 - `turbo build --filter=docs --dry`: Quickly print an outline of the `build` task for your `docs` package (without running it)
@@ -134,20 +112,13 @@ Once installed globally, you can run your scripts through `turbo` from your term
   `turbo build` and `turbo run build` will both run your `build` task.
 </Callout>
 
-<Callout type="error" title="Avoid multiple global installations">
-  If you've installed global `turbo` before, make sure you use the same package
-  manager as your existing installation to avoid unexpected behaviors. You can
-  quickly check which package manager you previously used with [`turbo
-  bin`](/docs/reference/bin).
-</Callout>
-
 #### Using global `turbo` in CI
 
-You can also take advantage of global `turbo` when creating your CI pipelines. Visit the [Constructing CI](/docs/crafting-your-repository/constructing-ci#global-turbo-in-ci) guide for more information.
+To use the global binary in CI, see [Constructing CI](/docs/crafting-your-repository/constructing-ci#global-turbo-in-ci).
 
 ### Repository installation
 
-When collaborating with other developers in a repository, it's a good idea to pin versions of dependencies. You can do this with `turbo` by adding it as a `devDependency` in the root of your repository:
+To pin the `turbo` version used in a repository, add it as a `devDependency` at the root:
 
 <PackageManagerTabs>
 
@@ -196,6 +167,4 @@ When collaborating with other developers in a repository, it's a good idea to pi
 
 </PackageManagerTabs>
 
-You can continue to use your global installation of `turbo` to run commands. Global `turbo` will defer to the local version of your repository if it exists.
-
-This lets you to get the best of both installations: easily run commands in your terminal while maintaining a pinned version for consistent usage for all developers in the repository.
+When you invoke the global binary from this repository, it uses the installed local version instead.

package/docs/guides/migrating-from-nx.mdx

@@ -471,60 +471,24 @@ aube add turbo --save-dev
 
 </PackageManagerTabs>
 
-You can also optionally install `turbo` globally for added convenience when working with Turborepo.
+To run `turbo` directly from your terminal, install the global binary:
 
-<PackageManagerTabs>
-
-<Tab value="pnpm">
+<Tabs items={["macOS and Linux", "Windows x64"]}>
+  <Tab value="macOS and Linux">
 
-```bash title="Terminal"
-pnpm add turbo --global
+```sh title="Terminal"
+curl -fsSL https://turborepo.dev/install | sh
 ```
 
-</Tab>
+  </Tab>
+  <Tab value="Windows x64">
 
-<Tab value="yarn">
-
-```bash title="Terminal"
-yarn global add turbo
+```powershell title="PowerShell"
+irm https://turborepo.dev/install.ps1 | iex
 ```
 
-</Tab>
-
-<Tab value="npm">
-
-```bash title="Terminal"
-npm install turbo --global
-```
-
-</Tab>
-
-<Tab value="bun">
-
-```bash title="Terminal"
-bun install turbo --global
-```
-
-</Tab>
-
-
-<Tab value="nub">
-
-```bash title="Terminal"
-nub add turbo --global
-```
-
-</Tab>
-
-<Tab value="aube">
-
-```bash title="Terminal"
-aube add turbo --global
-```
-
-</Tab>
-
-</PackageManagerTabs>
+  </Tab>
+</Tabs>
 
 ### Step 8: Add a `turbo.json`
 

package/docs/guides/tools/docker.mdx

@@ -144,6 +144,8 @@ docker build -f apps/web/Dockerfile .
   mode](https://nextjs.org/docs/pages/api-reference/next-config-js/output).
 </Callout>
 
+Standalone release archives start at 2.11.5. To use an older `turbo` version, install it with your package manager in the `prepare` stage instead of downloading an archive (for example, `RUN yarn global add turbo@2.11.4`).
+
 ```docker title="./apps/web/Dockerfile"
 FROM node:18-alpine AS base
 RUN apk update
@@ -153,9 +155,27 @@ WORKDIR /app
 
 # ---
 FROM base AS prepare
-# Replace <your-major-version> with the major version installed in your repository. For example:
-# RUN yarn global add turbo@^2
-RUN yarn global add turbo@^<your-major-version>
+RUN apk add --no-cache curl
+# Pin a release compatible with the turbo version in your repository.
+ARG TURBO_VERSION=2.11.5
+RUN set -eu; \
+    case "$(uname -m)" in \
+      x86_64) target=x86_64-unknown-linux-musl ;; \
+      aarch64) target=aarch64-unknown-linux-musl ;; \
+      *) echo 'Unsupported architecture' >&2; exit 1 ;; \
+    esac; \
+    archive="turbo-$TURBO_VERSION-$target.tar.gz"; \
+    release="https://github.com/vercel/turborepo/releases/download/v$TURBO_VERSION"; \
+    cd /tmp; \
+    curl -fsSL "$release/SHA256SUMS" -o SHA256SUMS; \
+    curl -fsSL "$release/$archive" -o "$archive"; \
+    awk -v name="$archive" '$2 == name && NF == 2 { print }' SHA256SUMS > turbo-checksum; \
+    [ "$(wc -l < turbo-checksum)" -eq 1 ]; \
+    sha256sum -c turbo-checksum; \
+    [ "$(tar -tzf "$archive")" = turbo ]; \
+    tar -xzf "$archive" -C /usr/local/bin turbo; \
+    chmod 755 /usr/local/bin/turbo; \
+    rm SHA256SUMS turbo-checksum "$archive"
 COPY . .
 # Add lockfile and package.json's of isolated subworkspace
 # Generate a partial monorepo with a pruned lockfile for a target workspace.

package/docs/reference/bin.mdx

@@ -12,6 +12,6 @@ Get the path to the `turbo` binary.
 turbo bin
 ```
 
-When using [**global `turbo`**](/docs/getting-started/installation#global-installation), this will be the path to the global `turbo` binary. You're likely to see a path to the global directory of the package manager you used to install `turbo`.
+When using [**global `turbo`**](/docs/getting-started/installation#global-installation), this will be the path to the global binary, such as `~/.local/bin/turbo` on macOS/Linux or `%LOCALAPPDATA%\Programs\Turborepo\bin\turbo.exe` on Windows.
 
 When using [**local `turbo`**](/docs/getting-started/installation#repository-installation), this will be the path to the local `turbo` binary. When `turbo` is installed in your repository, it is likely to be a path to `node_modules`.

package/docs/reference/configuration.mdx

@@ -582,9 +582,9 @@ When enabled, Turborepo will honor the `experimentalObservability.otel` configur
 }
 ```
 
-Adds a tag to a package for use with [Boundaries](/docs/reference/boundaries).
+Adds arbitrary string labels to a package. Labels do not need to be registered in `boundaries.tags`. Package tags can still be used with [Boundaries](/docs/reference/boundaries); existing boundary rules are unchanged.
 
-This key only works in [Package Configurations](/docs/reference/package-configurations). Using this key in a root `turbo.json` will result in an error.
+Top-level tags label the package containing the configuration. Root `turbo.json` tags label the root package, not every package in the repository. Package tags are separate from task tags and are not inherited through task configuration.
 
 ### `global`
 
@@ -665,6 +665,40 @@ In the example below, we've defined three tasks under the `tasks` key: `build`,
 
 Using the options available in the tasks you define in `tasks`, you can describe how `turbo` will run your tasks.
 
+### Task tags
+
+Add `tags` to a task definition in the root `turbo.json` or a [Package Configuration](/docs/reference/package-configurations):
+
+```jsonc title="./turbo.json"
+{
+  "tasks": {
+    "test": {
+      "tags": ["ci", "slow"],
+    },
+  },
+}
+```
+
+Task tags are arbitrary string labels. Their configured order and duplicates are preserved. They do not change task dependencies, commands, or boundary rules.
+
+If a Package Configuration omits task `tags`, it inherits them. An explicit array replaces inherited task tags, and `"tags": []` clears them. To append labels instead of replacing them, use [`$TURBO_EXTENDS$`](#turbo_extends), just like other task array fields:
+
+```jsonc title="./apps/web/turbo.json"
+{
+  "extends": ["//"],
+  "tasks": {
+    "test": {
+      // Inherits "ci" and "slow", then adds "frontend"
+      "tags": ["$TURBO_EXTENDS$", "frontend"],
+    },
+  },
+}
+```
+
+The marker is removed from resolved task tags, yielding `["ci", "slow", "frontend"]`. The same inheritance and composition rules apply when extending task configuration from other packages. A task with `"extends": false` starts with fresh configuration rather than inherited tags. Clearing task tags does not remove package tags.
+
+Tags are not included in the resolved task hash data. However, changing tags in a package's `turbo.json` can still invalidate its cache when that file is included in the task's file inputs.
+
 ### `extends` (task-level)
 
 Controls whether a task inherits configuration from the extends chain. This option is only available in [Package Configurations](/docs/reference/package-configurations), not in the root `turbo.json`.
@@ -1022,6 +1056,7 @@ This microsyntax can be used in the following array fields:
 - `inputs`
 - `outputs`
 - `passThroughEnv`
+- Task `tags`
 - `with`
 
 For example, if your root `turbo.json` defines:

package/docs/reference/package-configurations.mdx

@@ -53,7 +53,9 @@ For example, if your root `turbo.json` sets `"outputLogs": "hash-only"` for a ta
 
 ### Array fields replace by default
 
-Array fields like `outputs`, `env`, `inputs`, `dependsOn`, and `passThroughEnv` **completely replace** the root configuration's values by default.
+Array fields like `outputs`, `env`, `inputs`, `dependsOn`, `passThroughEnv`, and task `tags` **completely replace** the root configuration's values by default.
+
+For task `tags`, omission inherits the labels, an explicit array replaces them, and `[]` clears them. Use `"tags": ["$TURBO_EXTENDS$", "frontend"]` to append to inherited labels instead. Top-level package tags remain separate: they label the current package rather than being inherited as task configuration.
 
 ```jsonc title="./turbo.json"
 {
@@ -94,7 +96,7 @@ To **add** to inherited array values instead of replacing them, use the [`$TURBO
 }
 ```
 
-The `$TURBO_EXTENDS$` marker must be the first element in the array. It works with `outputs`, `env`, `inputs`, `dependsOn`, `passThroughEnv`, and `with`.
+The `$TURBO_EXTENDS$` marker must be the first element in the array. It works with `outputs`, `env`, `inputs`, `dependsOn`, `passThroughEnv`, task `tags`, and `with`.
 
 ### Extending from other packages
 

package/docs/reference/query.mdx

@@ -114,6 +114,53 @@ expanded names, framework-inferred variables, or a complete process environment.
 The query does not execute tasks or report cache hits. Unlike dry-run summaries,
 this selection does not include file-hash inventories.
 
+## Package task catalogue
+
+`package.tasks` lists the package's native scripts and resolved Task Graph entries,
+including configured tasks without a script and tasks with an explicit command.
+Scriptless tasks can be entrypoints that depend on runnable tasks. Their `script`
+is `null`, and their `command` is `null` unless a command is configured. Inherited
+and shared configurations are resolved before listing tasks; scriptless tasks
+excluded by `extends: false` are not included. Task names are deduplicated and sorted.
+Task filters apply to this full catalogue, not only tasks with native scripts.
+
+## Tags
+
+Packages and tasks expose a `tags` array, returning `[]` when no labels are configured. Package tags come from the package's loaded `turbo.json` and do not include task labels or inherit root package labels.
+
+A task's `tags` contains its resolved task labels only, after configuration inheritance and `$TURBO_EXTENDS$` composition. Order and duplicate labels are preserved, and the inheritance marker is not exposed. Select `package { tags }` to read its package labels separately.
+
+Use `has: { field: TAG, value: "label" }` to filter by exact, case-sensitive membership. Package predicates match package labels only. Task predicates match either resolved task labels or package labels.
+
+```bash title="Terminal"
+turbo query '
+query {
+  packages(filter: {has: {field: TAG, value: "frontend"}}) {
+    items { name tags }
+  }
+  package(name: "web") {
+    tasks(filter: {has: {field: TAG, value: "ci"}}) {
+      items { fullName tags package { tags } }
+    }
+  }
+}
+'
+```
+
+Task predicates support `and`, `or`, and `not`, as well as `equal` and `notEqual` on `NAME`, `FULL_NAME`, and `EXPERIMENTAL_CI`. `EXPERIMENTAL_CI` compares the resolved `experimentalCI` metadata as JSON: a boolean, an object, or `null` when unset. Objects use structural equality, not partial matching. An omitted predicate `value` is equivalent to explicit `null`. `NAME` and `FULL_NAME` equality still only matches strings, and `TAG` membership still only matches string labels. To select configured values other than `false`, combine `notEqual: {field: EXPERIMENTAL_CI, value: null}` and `notEqual: {field: EXPERIMENTAL_CI, value: false}` with `and`. This comparison does not interpret metadata contents or assign meaning to tags. The optional task `filter` is available on package task lists, task dependency/dependent lists, and `withDependencies`.
+
+For affected tasks, pass `taskFilter` alongside the existing package `filter` or task-name `tasks` arguments:
+
+```graphql title="ci-plan.gql"
+query {
+  affectedTasks(base: "origin/main", head: "HEAD", taskFilter: {has: {field: TAG, value: "ci"}}) {
+    items { fullName tags package { tags } }
+  }
+}
+```
+
+Affected-task filters intersect before required prerequisites are added, so prerequisites may not carry the selected tag. Filters on dependency/dependent lists and `withDependencies` apply after traversal; they narrow the returned list without pruning traversal through non-matching tasks.
+
 ## Shorthands
 
 Shorthands generate GraphQL queries for common operations so you don't need to write them by hand. The JSON output is identical to what you'd get from a raw query.

package/docs/reference/run.mdx

@@ -117,6 +117,16 @@ turbo run build --cache=local:rw
 turbo run build --cache=local:,remote:r
 ```
 
+### `--cache-workers <number>`
+
+Default: `10`
+
+Set the number of concurrent cache operations.
+
+```bash title="Terminal"
+turbo run build --cache-workers=4
+```
+
 ### `--cache-dir <path>`
 
 Default: `.turbo/cache`
@@ -279,6 +289,30 @@ Filters can be combined to create combinations of packages, directories, and git
 
 For in-depth discussion and practical use cases of filtering, visit [the Running Tasks page](/docs/crafting-your-repository/running-tasks).
 
+#### Filtering by tag
+
+Use `tag:<label>` to select tasks with a matching [task or package tag](/docs/reference/configuration#task-tags). A package tag matches every requested task in that package; a task tag matches only tasks carrying that label. No future flag is required.
+
+```bash title="Terminal"
+turbo run test --filter=tag:ci
+turbo run test --filter=tag:ci --filter='!tag:slow'
+turbo run test --affected --filter=tag:ci
+```
+
+Labels match exactly and case-sensitively, not as globs. Multiple include filters form a union; exclusions remove selected tasks. Required dependencies and co-scheduled `with` tasks are still retained, even if they do not match the tag.
+
+The `...` and `^` modifiers on tag selectors traverse the Task Graph: `...tag:ci` includes dependents and `tag:ci...` includes dependencies. Directory and Git qualifiers can further narrow a tag selector, for example `tag:ci{./apps/*}[HEAD^1]`. Git-qualified tag selectors match changed files against task inputs.
+
+For labels containing selector syntax, use a JSON string after `tag:` and preserve the double quotes with shell quoting:
+
+```bash title="Terminal"
+# Match the literal label "ci...", rather than expanding dependencies
+turbo run test --filter='tag:"ci..."'
+
+# Match the literal label "ci[main]{dir}"
+turbo run test --filter='tag:"ci[main]{dir}"'
+```
+
 #### Using a task identifier
 
 You can also run a specific task for a specific package in the format of `package-name#task-name`.
@@ -647,6 +681,14 @@ Ignore the local filesystem cache for all tasks, using Remote Cache for reading
 turbo run build --remote-only
 ```
 
+### `--single-package`
+
+Run `turbo` in [single-package workspace](/docs/guides/single-package-workspaces) mode, treating the repository as one package instead of discovering workspace packages.
+
+```bash title="Terminal"
+turbo run build --single-package
+```
+
 ### `--summarize`
 
 Generates a JSON file in `.turbo/runs` containing metadata about the run, including:

package/docs/reference/system-environment-variables.mdx

@@ -122,6 +122,16 @@ System environment variables are always overridden by flag values provided direc
         if one is not found.
       </td>
     </tr>
+    <tr id="turbo_env_mode">
+      <td>
+        <code>TURBO_ENV_MODE</code>
+      </td>
+      <td>
+        <span>Sets the environment mode, similar to using the</span>{" "}
+        <code>[--env-mode](/docs/reference/run#--env-mode-option)</code>
+        <span> flag.</span>
+      </td>
+    </tr>
     <tr id="turbo_force">
       <td>
         <code>TURBO_FORCE</code>
@@ -274,6 +284,15 @@ System environment variables are always overridden by flag values provided direc
       </td>
       <td>Always ignore the local filesystem cache for all tasks.</td>
     </tr>
+    <tr id="turbo_root_turbo_json">
+      <td>
+        <code>TURBO_ROOT_TURBO_JSON</code>
+      </td>
+      <td>
+        Use the <code>turbo.json</code> located at the provided path instead of
+        the one at the root of the repository.
+      </td>
+    </tr>
     <tr id="turbo_run_summary">
       <td>
         <code>TURBO_RUN_SUMMARY</code>
@@ -338,6 +357,15 @@ System environment variables are always overridden by flag values provided direc
         <a href="/docs/core-concepts/remote-caching">Remote Cache</a>.
       </td>
     </tr>
+    <tr id="turbo_tui_scrollback_length">
+      <td>
+        <code>TURBO_TUI_SCROLLBACK_LENGTH</code>
+      </td>
+      <td>
+        Number of lines to keep in scrollback for each task in the terminal
+        UI. Defaults to <code>2048</code>.
+      </td>
+    </tr>
     <tr id="turbo_ui">
       <td>
         <code>TURBO_UI</code>
@@ -346,6 +374,15 @@ System environment variables are always overridden by flag values provided direc
         Enables TUI when passed true or 1, disables when passed false or 0.
       </td>
     </tr>
+    <tr id="turbo_watch_startup_timeout">
+      <td>
+        <code>TURBO_WATCH_STARTUP_TIMEOUT</code>
+      </td>
+      <td>
+        Number of seconds <code>turbo watch</code> waits for the file watcher
+        to become ready before failing. Defaults to <code>120</code>.
+      </td>
+    </tr>
     <tr id="turbo_concurrency">
       <td>
         <code>TURBO_CONCURRENCY</code>

package/package.json

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

package/schema.json

@@ -191,7 +191,7 @@
       ]
     },
     "tags": {
-      "description": "Used to tag a package for boundaries rules.\n\nBoundaries rules can restrict which packages a tag group can import or be imported by.",
+      "description": "Arbitrary string labels for this package. In the root configuration, these labels apply to the root package.",
       "anyOf": [
         {
           "$ref": "#/definitions/Array_of_String"
@@ -678,6 +678,13 @@
             }
           ]
         },
+        "tags": {
+          "description": "Arbitrary string labels for this task. Package configurations replace inherited tags by default; an empty array clears them. Include `$TURBO_EXTENDS$` to append labels to inherited tags.",
+          "type": ["array", "null"],
+          "items": {
+            "$ref": "#/definitions/String"
+          }
+        },
         "with": {
           "description": "A list of tasks that will run alongside this task.\n\nTasks in this list will not be run until completion before this task starts execution.\n\nDocumentation: https://turborepo.dev/docs/reference/configuration#with",
           "type": ["array", "null"],