what stackpulse tracks
Turborepo releases from GitHub
StackPulse watches Turborepo release notes and keeps the original source link close to every summary.
High-performance build system for JavaScript and TypeScript monorepos StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Turborepo release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This canary release fixes directory-link handling in manual input hashing. It also updates the @vercel/geistdocs dependency.
Users relying on manual input hashing may be affected by the directory-link fix.
This canary adds a `turborepo@add` skill and a `--verbose` option to `turbo setup`. Setup now runs dependency installs in parallel, and its installer output is safe for concurrent installers.
Users of `turbo setup` can enable verbose output and benefit from parallel dependency installs; users of the `turborepo@add` skill can access the new skill.
This canary release adds task log-file and task-hash fields to `turbo query`. It also includes fixes for input hashing, affected-task detection, task execution, CLI reporting, and environment handling, along with dependency updates to patched versions.
Turborepo users are affected, particularly those using `turbo query`, affected-task detection, or task input hashing.
Review the new task fields in `turbo query` if you consume its output; the release notes do not specify additional upgrade steps.
Turborepo 2.11.11 improves `turbo setup` with redesigned terminal output, faster setup, progress reporting for `turbo.lock`, and a shared content-addressed store for managed tools. It also fixes caching, watch-mode behavior, lockfile handling, shell completion, and credential scoping; the notes do not describe a migration requirement.
Turborepo users may see changes to setup output and managed-tool storage, while users of caching, watch mode, or Vercel credentials benefit from fixes in those areas.
This canary release adds and improves managed-tool setup, including a shared content-addressed store, clearer setup output, and faster setup and lockfile creation. It also includes shell completion and lockfile-comparison fixes, plus performance improvements to environment matching.
Users of turbo setup and managed tools will see changes to tool storage and setup behavior, with improved performance and clearer progress output.
This canary release includes fixes across caching, task hashing and affected-task detection, package-manager support, and watch mode. It also redesigns `turbo setup` terminal output and includes a security fix that restricts saved Vercel credentials to Vercel endpoints.
Turborepo users may benefit from more reliable caching, task detection, and watch behavior; users of `turbo setup` will see revised output and removed setup controls.
As this is a canary prerelease, test it in a non-production environment before adopting it.
This release includes several bug fixes and minor improvements, particularly for Windows users and pnpm compatibility. It also adds WebMCP support for Turborepo documentation.
Users on Windows or using pnpm may experience improved stability and performance.
Update to v2.11.10 for bug fixes and minor improvements.
This release focuses on performance optimizations and introduces new features related to setup plans and tool provisioning. Numerous improvements have been made to lockfile handling, cache operations, and task execution efficiency.
Users relying on Turborepo for large-scale monorepo management will benefit from the performance improvements.
This release focuses on improvements to setup and lockfile management, including provisioning frozen Node and pnpm, validating tool readiness, and resolving verified registry artifacts. Performance optimizations for lockfile loading and cache handling are also included.
Users of Turborepo's setup and lockfile management features may be affected by the changes.
Review the changes to setup and lockfile management if you use these features.
This release introduces several experimental setup features, including bounded checksum-verifying downloads and Node version resolution from native declarations. It also includes various fixes and improvements to the setup process.
Developers using Turborepo's experimental setup features or managing Node.js versions may be affected by the changes.
Review the new experimental setup features and consider testing them in a non-production environment.
This canary release includes fixes for duplicate package name generation and JavaScript tool selection reconciliation, along with a security upgrade for Next.js to address CVE-2026-94483.
Users relying on JavaScript tool selections or affected by CVE-2026-94483 should take note.
Upgrade to this version if you are affected by CVE-2026-94483 or need JavaScript tool selection fixes.
This canary release introduces several experimental features, including task tags, setup command surfaces, and bounded checksum-verifying downloads. It also includes various fixes for task input normalization, standalone Turbo installation, and repository task handling.
Developers using Turborepo for task management and package filtering may benefit from the new tagging and query features.
Consider testing the new task tagging and query features in a non-production environment.
This release includes minor fixes and updates, such as passing SDKROOT to repository tasks and ignoring Vercel OIDC token rotation in .env.local cache inputs.
Users relying on SDKROOT in repository tasks or Vercel OIDC token rotation in .env.local cache inputs may be affected.
This release focuses on improving task management and query capabilities, along with several bug fixes and documentation updates. Key changes include the introduction of task tags for better organization and filtering, as well as enhancements to the `query` command.
Users leveraging task management and querying in Turborepo will benefit from the new tagging and filtering features.
Update to v2.11.6 to take advantage of new task tagging and query capabilities.
This release focuses on internal test improvements, dependency updates, and minor fixes. Key changes include bundling documentation in the `turbo` npm package, addressing a security vulnerability in `js-yaml`, and stabilizing pnpm per-workspace lockfile hashes.
Users relying on `js-yaml` or Next.js in their Turborepo setup should update to mitigate security vulnerabilities.
Update to Turborepo v2.11.5 to address security vulnerabilities and benefit from minor fixes.
This release introduces standalone installer URLs for easier installation via `curl | bash` and includes a fix to isolate the installer test environment.
Users who prefer installing Turborepo via `curl | bash` will benefit from the new standalone installer URLs.
This canary release includes minor fixes and a new feature for publishing versioned standalone turbo archives. It also updates documentation and fixes a release job issue.
This release primarily focuses on dependency updates, security fixes, and performance improvements. It includes updates to address CVEs in js-yaml and Next.js, along with various Rust dependency cleanups and performance optimizations.
Users relying on specific dependencies or Rust APIs may be affected by dependency removals and API cleanups.
Update to the latest version to benefit from security fixes and performance improvements.
This canary release includes minor test improvements and a new feature to bundle documentation in the `turbo` npm package.
This release focuses on bug fixes, performance improvements, and refactoring, particularly around Go and Cargo toolchain integration, remote cache handling, and affected task detection.
Developers using Turborepo with Go or Cargo toolchains may be affected by changes in task detection and cache handling.