turbo
2.11.13 · 18 Nov 2026MIT48.2M / weekRepositoryHomepagenpmAtom feed
Upgrading turbo From 2.10.5 to 2.11.13
22 releases in betweenevery note read
- 2
- changes to make
- 0
- advisories fixed
- 455
- new
- 352
- fixes
Before you upgrade
Tick each one off as you go- Breaking2.11.0
- Breaking2.11.0
Security
- 2.11.5
Update js-yaml to address CVE-2026-84375
- 2.11.0
Reject output path traversal
- 2.11.0
Bump tar to 7.5.22 in @turbo/releaser (CVE-2026-73566)
Release by release
- Fixed
Make the
turbo tracegraph directory followcacheMaxAgeandcacheMaxSize - Fixed
Scope root JavaScript dependencies to JavaScript and root tasks
- Fixed
- New
Add
turborepo@addskill - New
Add
--verboseto turbo setup - New
Run turbo setup dependency installs in parallel
- New
Support pnpm v13 lockfiles
- New
- New
Stop requiring
.turbo/to be Git-ignored in turbo setup - New
Redesign turbo setup terminal output
- New
Add canary version to standalone installers
- New
Speed up prefix environment matching
- New
- New
Enable WebMCP for Turborepo docs
- Fixed
Allow non-recursive Turbo commands in root tasks
- Fixed
Avoid pnpm batch-shim shutdown hangs on Windows
- Fixed
Exclude tool-managed directories from local dependency inputs
- New
- New
Prefetch Cargo metadata during lazy graph construction
- New
Compute Berry lockfile closures once across workspaces
- New
Check cache hit outputs in place instead of on the blocking pool
- New
Speed up Berry lockfile loading
- New
- New
Add experimental setup future flag
- New
Add shared platform primitives for setup and shim
- New
Add bounded checksum-verifying downloads
- New
Validate setup npm version requests
- New
- Fixed
Pass SDKROOT through to repository tasks
- Fixed
Ignore Vercel OIDC token rotation in .env.local cache inputs
- Fixed
- New
Add task tags with configuration inheritance
- New
Expose task and package tags in
query - New
Filter
querytasks and packages by tags - New
Filter tasks by tags in the CLI
- New
880 internal lines (docs, tests, tooling) left out.
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.