Impact Score: 5/10
Turborepo v2.9.11
Source available — automated, not human-reviewed
Component: turbo · Channel: stable. Automated analysis, not a compatibility certification. How this works.
Analysis updated: 2026-11-01.
⚡ Executive Summary (TL;DR)
Turborepo v2.9.11. Source highlight: release(turborepo): 2.9.10 by @github-actions[bot] in https://github.com/vercel/turborepo/pull/12745
Who Does This Impact? (Role-Based Analysis)
💻 Software Engineers & Devs
Check the source notes against the package and APIs you use before upgrading.
📊 Product & Engineering Leads
Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.
⚙️ DevOps & Security
Verify the target version, runtime requirements and rollback procedure in the official documentation.
🔧 Bug Fixes & Patches (6)
- fix: Start daemon for VSCode Extension from the extension itself
- fix: Include file URIs in LSP lifecycle logs
- fix: Handle JSON decoration visitor depth
- fix: Resolve relative `turbo path` in VS Code extension
- fix: Preserve Bun nested dependencies during prune
- fix: Prefer installed Turbo for LSP
📄 View Raw Release Notes (Original Developer Log)
<!-- Release notes generated using configuration in .github/release.yml at v2.9.11 -->
## What's Changed
### Changelog
* release(turborepo): 2.9.10 by @github-actions[bot] in https://github.com/vercel/turborepo/pull/12745
* ci: Publish VS Code extension on release by @anthonyshew in https://github.com/vercel/turborepo/pull/12747
* fix: Start daemon for VSCode Extension from the extension itself by @anthonyshew in https://github.com/vercel/turborepo/pull/12749
* release(turborepo): 2.9.11-canary.1 by @github-actions[bot] in https://github.com/vercel/turborepo/pull/12748
* fix: Include file URIs in LSP lifecycle logs by @anthonyshew in https://github.com/vercel/turborepo/pull/12751
* fix: Handle JSON decoration visitor depth by @anthonyshew in https://github.com/vercel/turborepo/pull/12752
* fix: Resolve relative `turbo path` in VS Code extension by @anthonyshew in https://github.com/vercel/turborepo/pull/12753
* fix: Preserve Bun nested dependencies during prune by @anthonyshew in https://github.com/vercel/turborepo/pull/12754
* fix: Prefer installed Turbo for LSP by @anthonyshew in https://github.com/vercel/turborepo/pull/12755
* release(turborepo): 2.9.11-canary.2 by @github-actions[bot] in https://github.com/vercel/turborepo/pull/12750
* ci: Parallelize LSP release publishing by @anthonyshew in https://github.com/vercel/turborepo/pull/12758
* fix: Reduce VS Code extension startup popups by @anthonyshew in https://github.com/vercel/turborepo/pull/12759
* fix: Support `turbo.jsonc` in VS Code extension by @anthonyshew in https://github.com/vercel/turborepo/pull/12760
* fix: Remove VS Code task key gradient by @anthonyshew in https://github.com/vercel/turborepo/pull/12761
* release(turborepo): 2.9.11-canary.3 by @github-actions[bot] in https://github.com/vercel/turborepo/pull/12756
* chore: Release v2.9.11-canary.4 by @anthonyshew in https://github.com/vercel/turborepo/pull/12762
* ci: Stop VS Code publish from blocking release PR by @anthonyshew in https://github.com/vercel/turborepo/pull/12763
* release(turborepo): 2.9.11-canary.5 by @github-actions[bot] in https://github.com/vercel/turborepo/pull/12764
* fix: Publish VS Code extension from release tag by @anthonyshew in https://github.com/vercel/turborepo/pull/12765
* fix: Support shimmed VS Code LSP probes by @anthonyshew in https://github.com/vercel/turborepo/pull/12767
* release(turborepo): 2.9.11-canary.6 by @github-actions[bot] in https://github.com/vercel/turborepo/pull/12766
* release(turborepo): 2.9.11-canary.7 by @github-actions[bot] in https://github.com/vercel/turborepo/pull/12768
* fix: Allow `$TURBO_EXTENDS$` in LSP diagnostics by @anthonyshew in https://github.com/vercel/turborepo/pull/12770
**Full Changelog**: https://github.com/vercel/turborepo/compare/v2.9.10...v2.9.11