Skip to content

chore: Deprecate the turbo scan command#12406

Merged
anthonyshew merged 3 commits intomainfrom
shew/deprecate-scan-command
Mar 20, 2026
Merged

chore: Deprecate the turbo scan command#12406
anthonyshew merged 3 commits intomainfrom
shew/deprecate-scan-command

Conversation

@anthonyshew
Copy link
Contributor

Summary

Deprecates turbo scan and removes all of its implementation code. The diagnostics it ran have become irrelevant as turbo has evolved:

  • Turbo no longer shells out to Git, so configuring Git's FS Monitor daemon provides no benefit to turbo performance.
  • The Turborepo daemon is no longer used for turbo run, making the daemon health check unnecessary.
  • Remote Cache linking should be automatic and frictionless, not gated behind an interactive wizard. We have better flows for this now.
  • The LSP check is premature -- we don't want to actively push users toward the extension at this stage.
  • Version update checks are better handled by existing tooling (e.g. npx @turbo/codemod update), not an interactive prompt.

Since every diagnostic turbo scan ran is now either obsolete or better served elsewhere, the command itself no longer provides value.

What changed

  • Deleted the turborepo-diagnostics crate and the commands/scan.rs implementation.
  • turbo scan is now hidden from --help and prints a deprecation warning if invoked.
  • Documentation updated: reference page shows a deprecation callout, reference index card marked deprecated, and turbo scan added to the deprecated list on the support policy page.

@anthonyshew anthonyshew requested a review from a team as a code owner March 20, 2026 19:59
@anthonyshew anthonyshew requested review from tknickman and removed request for a team March 20, 2026 19:59
@vercel
Copy link
Contributor

vercel bot commented Mar 20, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
examples-basic-web Ready Ready Preview, Comment, Open in v0 Mar 20, 2026 9:24pm
examples-designsystem-docs Ready Ready Preview, Comment, Open in v0 Mar 20, 2026 9:24pm
examples-gatsby-web Ready Ready Preview, Comment, Open in v0 Mar 20, 2026 9:24pm
examples-kitchensink-blog Ready Ready Preview, Comment, Open in v0 Mar 20, 2026 9:24pm
examples-nonmonorepo Ready Ready Preview, Comment, Open in v0 Mar 20, 2026 9:24pm
examples-svelte-web Ready Ready Preview, Comment, Open in v0 Mar 20, 2026 9:24pm
examples-tailwind-web Ready Ready Preview, Comment, Open in v0 Mar 20, 2026 9:24pm
examples-vite-web Ready Ready Preview, Comment, Open in v0 Mar 20, 2026 9:24pm
turbo-site Ready Ready Preview, Comment, Open in v0 Mar 20, 2026 9:24pm
turborepo-agents Ready Ready Preview, Comment, Open in v0 Mar 20, 2026 9:24pm

… the Next.js docs build to fail with "Module not found".

This commit fixes the issue reported at apps/docs/content/docs/reference/scan.mdx:9

**Bug:** The file `apps/docs/content/docs/reference/scan.mdx` contains `import { Callout } from '#/components/callout';` on line 9. This module path `#/components/callout` does not resolve to any file — there is no `#` path alias configured in tsconfig.json or package.json imports, and no `callout.tsx` exists at that path. The `Callout` component is provided globally through `apps/docs/components/geistdocs/mdx-components.tsx`, and all 6 other MDX files in the same directory use `<Callout>` without any import.

This causes the Next.js docs build to fail with `Module not found: Can't resolve '#/components/callout'`.

**Fix:** Remove the broken `import { Callout } from '#/components/callout';` line from `scan.mdx`. The `<Callout>` component usage remains and will work correctly via the global MDX component injection, matching the pattern used by every other file in the directory.

Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: anthonyshew <[email protected]>
@anthonyshew anthonyshew merged commit 4a12c26 into main Mar 20, 2026
87 of 89 checks passed
@anthonyshew anthonyshew deleted the shew/deprecate-scan-command branch March 20, 2026 21:35
github-actions bot added a commit that referenced this pull request Mar 20, 2026
## Release v2.8.21-canary.2

Versioned docs: https://v2-8-21-canary-2.turborepo.dev

### Changes

- fix: Strip JSX components from heading anchors and TOC entries
(#12404) (`3abe553`)
- fix: Move docs app icons into app/ directory (#12403) (`ddf3918`)
- feat: Add experimental structured logging with `--json` and
`--log-file` flags (#12405) (`7ca0601`)
- release(turborepo): 2.8.21-canary.1 (#12407) (`adebb95`)
- docs: Downgrade Next.js (#12408) (`281e89b`)
- chore: Deprecate the `turbo scan` command (#12406) (`4a12c26`)

Co-authored-by: Turbobot <[email protected]>
github-actions bot added a commit that referenced this pull request Mar 23, 2026
## Release v2.8.21-canary.3

Versioned docs: https://v2-8-21-canary-3.turborepo.dev

### Changes

- chore: Deprecate the `turbo scan` command (#12406) (`4a12c26`)
- release(turborepo): 2.8.21-canary.2 (#12409) (`b9ef212`)
- fix(eslint-plugin-turbo): Guard against missing tasks/pipeline in
forEachTaskDef (#12411) (`6c107c2`)

Co-authored-by: Turbobot <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant