# vercel/turborepo · RepoSense Release & Migration Intelligence

> Faster lockfile creation and shared tool store. Test in staging; do not deploy to prod. Migration: Low.

## Metadata
- **Repository URL**: https://github.com/vercel/turborepo
- **Primary Package**: `turbo` (NPM)
- **Categories**: `BUILD_TOOL`
- **Latest Version**: `v2.11.11-canary.2`
- **Semantic Status**: `WARNING`
- **Bundle Size Impact (unavailable)**: `Size Unavailable`
- **Atom Ingestion Feed**: https://github.com/vercel/turborepo/releases.atom

## The Human Context (Plain-English Pitch)
Turborepo is a high-performance build system designed for JavaScript and TypeScript monorepos. As multi-package codebases grow, CI pipelines and local builds often duplicate work and severely slow down development. Turborepo accelerates workflows by executing tasks in parallel, managing dependency graphs, and caching computation results so teams never recompile the same code twice.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
Faster lockfile creation and shared tool store. Test in staging; do not deploy to prod. Migration: Low.

## Breaking Changes & Required Actions
- Accelerated `turbo.lock` generation, making lockfile creation approximately 10x faster.
- Introduced a shared content-addressed store for managed tools under `~/.local/share` on macOS, validating setups once instead of every run.
- Fixed package graph invalidation to scope `pnpm` `overrides` changes strictly to affected packages.
- Restored CLI shell completion and streamlined `turbo setup --plan` terminal formatting.

## Migration Snippet
```ts
npm install turbo@2.11.11-canary.2 --save-dev
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **Node.js >=18** [`COMPATIBLE`]: Native binary and CLI runtime support remains aligned with standard LTS Node.js environments.
- **pnpm >=8** [`COMPATIBLE`]: Scoping for pnpm overrides now strictly isolates diff detection to directly affected workspace packages.

## Zero-Noise Release Timeline
- **v2.11.11-canary.2** (2026-11-06) [WARNING]: Faster lockfile creation and shared tool store. Test in staging; do not deploy to prod. Migration: Low.
- **v2.11.11-canary.1** (2026-10-29) [WARNING]: chore: Release Turborepo 2.11.9-canary.1 by @github-action. Pre-release build; test in staging. Migration: Low.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is vercel/turborepo v2.11.11-canary.2 safe to upgrade in production?
vercel/turborepo v2.11.11-canary.2 is classified as WARNING (PRERELEASE release). Faster lockfile creation and shared tool store. Test in staging; do not deploy to prod. Migration: Low.

### What breaking changes or compatibility risks exist in vercel/turborepo v2.11.11-canary.2?
No breaking API changes or peer dependency conflicts are recorded for vercel/turborepo v2.11.11-canary.2 in the RepoSense compatibility graph.

### What is the bundle size impact of turbo v2.11.11-canary.2?
Measured bundle size telemetry is currently unavailable for turbo v2.11.11-canary.2; verify build output locally before deploying.

### How do I upgrade turbo to v2.11.11-canary.2?
Upgrade turbo to v2.11.11-canary.2 by running "npm install turbo@2.11.11-canary.2" and applying the migration steps: npm install turbo@2.11.11-canary.2 --save-dev