[33m"turbo-ignore" is deprecated. Use "turbo query affected

Error message

[33m"turbo-ignore" is deprecated. Use "turbo query affected" instead.[39m

What it means

Outside Vercel (VERCEL !== '1'), turbo-ignore's deprecation warning instead points to `turbo query affected`, the supported way to determine affected workspaces. The command continues to run and return its normal exit code; only the guidance text differs based on the environment.

Source

Thrown at packages/turbo-ignore/src/ignore.ts:53

) {
  opts.telemetry?.trackCommandStatus({ command: "ignore", status: "start" });
  opts.telemetry?.trackArgumentWorkspace(workspaceArg !== undefined);
  trackOptions(opts);

  const inputs = {
    workspace: workspaceArg,
    ...opts
  };

  if (process.env.VERCEL === "1") {
    warn(
      `\u001B[33m"turbo-ignore" is deprecated. Use Vercel's built-in project skipping instead.\u001B[39m`
    );
    warn(
      `\u001B[33mLearn more: https://vercel.com/docs/monorepos#skipping-unaffected-projects\u001B[39m\n`
    );
  } else {
    warn(
      `\u001B[33m"turbo-ignore" is deprecated. Use "turbo query affected" instead.\u001B[39m`
    );
    warn(
      `\u001B[33mLearn more: https://turborepo.dev/docs/reference/query#migrating-from-turbo-ignore\u001B[39m\n`
    );
  }

  info(
    `Using Turborepo to determine if this project is affected by the commit...\n`
  );

  // set default directory
  if (opts.directory) {
    const directory = path.resolve(opts.directory);
    if (existsSync(directory)) {
      inputs.directory = directory;
    } else {
      warn(

View on GitHub (pinned to f9245100cf)

Solutions

Replace turbo-ignore with `turbo query affected` (e.g. `turbo query affected --exit-code` to gate CI) and branch on its output
If immediate migration is not possible, keep turbo-ignore but track the migration — it still functions
Consult the linked guide (turborepo.dev/docs/reference/query#migrating-from-turbo-ignore)

Example fix

# before (CI step)
- run: npx turbo-ignore --scope=web

# after
- run: turbo query affected --packages=web --exit-code

Defensive patterns

Strategy: fallback

Validate before calling

# Replace the deprecated call in CI with the query command
# before: npx turbo-ignore --scope=web
# after:
turbo query affected --packages=web --exit-code

Prevention

Migrate pipelines to `turbo query affected` and use --exit-code to gate steps
Keep turbo-ignore only as a stopgap and track its removal as tech debt
Note the message varies by environment: VERCEL=1 shows the Vercel-specific guidance instead

When it happens

Trigger: CI scripts (GitHub Actions, GitLab, etc.) invoking `npx turbo-ignore` without VERCEL set, typically guarding per-package build jobs; the else-branch of the VERCEL check fires.

Common situations: Legacy CI pipelines built around turbo-ignore; teams planning the migration to `turbo query affected` (which supports --packages, --tasks, --base/--head, --exit-code).

Related errors

AI-assisted analysis of vercel/turborepo@f9245100cf (2026-08-17). Data as JSON: /api/errors/040638c2b2555160. Report an issue: GitHub.

[33m"turbo-ignore" is deprecated. Use "turbo query affected