turbo
2.11.13 · 18 Nov 2026MIT48.2M / weekRepositoryHomepagenpmAtom feed
Upgrading turbo From 1.10.14 to 1.10.15
1 release in betweenevery note read
Security
2 advisories still affect 1.10.15
- 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
turbopack: Emit raw image bytes for unsupported codec
- New
create-turbo: Support package manager opt
- New
Add progress and top self time to convert trace tool
- New
Add "toggleButton" to sidebar
- New
18 other lines we could not sort, mostly version bumps
- 1.10.15
Quiet a (mostly unaddressable) Sentry error
- 1.10.15
Sync deps
- 1.10.15
Link to Next.js issue link for Turbopack issues
- 1.10.15
libwebp-sys: 0.9.2 -> 0.9.3
- 1.10.15
Signal when signal handler is registered
- 1.10.15
Output logs docs update
- 1.10.15
Revert "Turbopack: add support for an asset prefix (and basePath in N…
- 1.10.15
Refactor TaskScopes to use an aggregation tree
- 1.10.15
feat(turbo-ignore) add a --max-buffer option for dry runs that have large outputs
- 1.10.15
Tracing improvements
14 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.