turbo
2.11.13 · 18 Nov 2026MIT48.2M / weekRepositoryHomepagenpmAtom feed
Upgrading turbo From 1.10.12 to 1.10.13
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 16
- new
- 17
- fixes
Before you upgrade
Tick each one off as you go- Breaking1.10.13
Security
2 advisories still affect 1.10.13
- Turbo: Unexpected local code execution during Yarn Berry detectionlow · GHSA-3qcw-2rhx-2726
- Turbo: Login callback CSRF/session fixationmoderate · GHSA-hcf7-66rw-9f5r
Upgrading to 2.9.14 clears them.
Release by release
- Breaking
Turborepo: Drop argument separator for yarn
- New
Allow fallback to be used outside VERCEL
- New
Wasm text format and import support
- New
turborepo: Port Async Cache and Cache Multiplexer
- Breaking
26 other lines we could not sort, mostly version bumps
- 1.10.13
Change READMEs of created turborepos (reflect appDir)
- 1.10.13
Export namespace object instead commonjs interop object
- 1.10.13
Revert "export namespace object instead commonjs interop object"
- 1.10.13
Remove require.cache clear from chunk loading
- 1.10.13
Snapshot tests: canonicalize with dunce
- 1.10.13
Turbopack: Sort env vars for compatibility
- 1.10.13
WEB-1278: Turbopack build: Implement minification with swc minify
- 1.10.13
Update swc_core and sync deps
- 1.10.13
no-context lint: migrate some crates
- 1.10.13
no-context: Migrate
turbopack-core
27 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.