turbo
2.11.13 · 18 Nov 2026MIT48.2M / weekRepositoryHomepagenpmAtom feed
Upgrading turbo From 1.9.3 to 1.9.4
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 7
- new
- 13
- fixes
Before you upgrade
Tick each one off as you go- Breaking1.9.4
Security
2 advisories still affect 1.9.4
- 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
No longer include peer dependencies in transitive closures
- New
turbo: Add spaces link
- New
Add rust implementation of Yarn3+ lockfile
- New
Use Rust Berry lockfile impl
- Breaking
32 other lines we could not sort, mostly version bumps
- 1.9.4
Env var run summary data generation
- 1.9.4
Include logs when posting task summary
- 1.9.4
Always print the url if we have one
- 1.9.4
Remove unused import
- 1.9.4
Use spaceID from turbo.json if available
- 1.9.4
port(turborepo): Config
- 1.9.4
Existing and error logs behavior
- 1.9.4
Update deps
- 1.9.4
Invoke prysk with the directory name to ensure all tests run
- 1.9.4
Move
TURBO_FORCEconfig env var detection to Rust
11 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.