turbo
2.11.13 · 18 Nov 2026MIT48.2M / weekRepositoryHomepagenpmAtom feed
Upgrading turbo From 2.1.1 to 2.1.2
1 release in betweenevery note read
Security
2 advisories still affect 2.1.2
- 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
- New
Update Prisma schema
- New
Allow for specifying path of root turbo.json
- New
tui: Only rerender if a non-tick event has been received
- Fixed
tui: Start pty with matching TUI size
- Fixed
filter: Validate package name on full graph
- Fixed
affected: Include dependents in affected filter
- New
2 other lines we could not sort, mostly version bumps
- 2.1.2
Remove alias for --daemon/--no-daemon
- 2.1.2
Removes references to docs from root package.json
10 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.