turbo
2.11.13 · 18 Nov 2026MIT48.2M / weekRepositoryHomepagenpmAtom feed
Upgrading turbo From 2.9.7 to 2.9.14
6 releases in betweenevery note read
- 0
- changes to make
- 2
- advisories fixed
- 1
- new
- 44
- fixes
Security
Fixes 2 advisories affecting 2.9.7
- Turbo: Unexpected local code execution during Yarn Berry detectionlow · GHSA-3qcw-2rhx-2726
- Turbo: Login callback CSRF/session fixationmoderate · GHSA-hcf7-66rw-9f5r
- 2.9.14
This release contains important security fixes.
- 2.9.14
- 2.9.14
- 2.9.14
Release by release
- Security
This release contains important security fixes.
- Security
- Security
- Security
- Security
- Fixed
Allow transit nodes in LSP diagnostics
- Fixed
- Fixed
Start daemon for VSCode Extension from the extension itself
- Fixed
Include file URIs in LSP lifecycle logs
- Fixed
Handle JSON decoration visitor depth
- Fixed
Resolve relative
turbo pathin VS Code extension
- Fixed
- Fixed
Respect SCM env vars in
turbo query affected - Fixed
Avoid some raw
create-turboexample telemetry - Fixed
Escape graph HTML payloads
- Fixed
Prevent OTEL token injection to spoofed origins
- Fixed
- Fixed
Remove Unix parent death watchdogs
- Fixed
Scope repo index prefixes to Git root
- Fixed
Harden OG image signatures
- Fixed
Scope release npm publishing credentials
- Fixed
Harden docs security endpoints
- Fixed
Preserve lockfiles during dry-run conversion
- Fixed
- New
Reduce
turbo watchhash memory spikes - Fixed
Preserve concrete dependency precedence
- Fixed
Resolve Yarn catalog affected packages
- Fixed
Preserve Bun prune lockfile validity
- Fixed
Create prune docker bin stubs
- Fixed
Keep tbx shell connections stable
- Fixed
Reduce parent-death watchdog CPU usage
- New
36 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.