turbo
2.11.13 · 18 Nov 2026MIT48.2M / weekRepositoryHomepagenpmAtom feed
Upgrading turbo From 1.12.5 to 1.13.4
5 releases in betweenevery note read
Security
2 advisories still affect 1.13.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
- New
turbo-ignore: don’t fail on single package repos
- New
Turborepo: Be explicit about which binary we failed to find
- New
Turborepo: Add support for $TURBO_DEFAULT$ to file hash watcher
- New
turborepo: Using file hashing for package watching
- New
- New
Use @repo/ pattern in
math-helpersexample, consistent with "getting started" and starter repo - New
turbo-ignore: Usage metrics
- New
telemetry: Defensive config loading
- New
Turborepo: Flag on daemon package discovery
- New
1.13.2nothing new or fixed in the note
- New
ui: Persist logs on failure
- New
Turborepo: Handle package manager changes
- New
ui: Add ability to scroll task output
- New
ui: Persist all logs
- New
- New
Support import.meta.env in eslint-plugin-turbo
- New
Add success rate telemetry for login
- New
Add invalidate flag to logout
- New
Terminal pane component
- New
4 other lines we could not sort, mostly version bumps
- 1.13.4
Remove async-trait from a few crates
- 1.13.4
Yield a different warning when the cache upload times out
- 1.13.3
Update lockfile for compatibility with next.js
- 1.13.0
Publish 1.13.0-canary.2 to registry
61 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.