turbo
2.11.13 · 18 Nov 2026MIT48.2M / weekRepositoryHomepagenpmAtom feed
2.11.13 is the newest release of 2.x.
In short
40 new1 faster26 fixed32 internal
Release note
What's Changed
Changelog
Add experimental setup future flag
Remove Bash dependency from strict environment tests
Use repository package manager for automatic Turbo downloads
Add shared platform primitives for setup and shim
Populate task graphs for affected and filtered listings
Add bounded checksum-verifying downloads
Validate setup npm version requests
Prune unused pnpm catalog snapshots
Resolve Node versions from native declarations
Honor tool-download proxy and certificate settings
Check bounded setup version-request overlap
Discover setup JavaScript package-manager declarations
Verify local artifact bytes without HTTP
Deflake concurrent agent guidance updates
Extract verified TAR archives into private staging
Add experimental setup command surface
Extract safe Node TAR symlinks
Infer setup roots without package managers
Add atomic managed tool installation inventory
Invalidate managed repositories when turbo.lock changes
Safely extract verified ZIP archives
Avoid duplicate code CI on pull request reviews
Validate portable setup tool resolutions
Preserve scoped tool paths and owner-executable exports
Preserve Node runtime failure policy provenance
Add an internal managed-run capability query
Verify bounded SHA-512 tool artifacts
Repair missing install generations and share tool readiness
Add secure ignored setup writer storage
Parse bounded Node release metadata
Write setup locks atomically
Parse bounded npm registry release metadata
Preserve unknown pnpm lockfile settings through prune
Preserve symlinked AGENTS.md when updating agent guidance
Compare setup source snapshots before lock publication
Provision locked pnpm with managed Node launchers
Resolve native Node.js declarations into lock selections
Reuse healthy Node.js across managed inventory changes
Support npm patches in pruned workspaces
Project selected managed execution identity
Skip ignored directories when discovering nested .gitignore files
Provision independently pinned npm with managed Node
Capture setup discovery context for revalidation
Stop
add-package-namescodemod from generating duplicate namesReconcile captured JavaScript tool selections
Share setup TLS and guard official source policy
Represent matching Node-bundled npm ownership
Preserve setup lock declarations during prune
Provision frozen Node and pnpm through setup
Exclude optional npm peers from pruned lockfiles
Validate managed Node and pnpm readiness
Resolve exact verified registry artifacts for setup locks
Check installed setup tools without mutation
Resolve captured Node and pnpm lock cohorts
Guard setup publication plans and discovery indirections
Release setup locks in their acquiring process
Create and reconcile local setup locks
Refresh managed setup locks explicitly
Force reinstall locked setup tools
Bind setup records to installation generations
Generalize repository bootstrap across toolchains
Keep Go discovery stable when the repository is reached through a symlink
Reject non-member local sources in the uv manifest fallback
Hash ruff and pytest configuration between the root and uv members
Hash Clippy configuration for Cargo lint tasks
Carry uv tool configuration into pruned workspaces
Report inferred framework env vars for deferred tasks in dry runs
Upgrade turbo-gen Handlebars to 4.7.10
Validate sealed native setup baselines
Prevent Git index refresh during dirty hash collection
Disable agent guidance by default
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.