Packages

turbo

2.11.13 · 18 Nov 2026MIT48.2M / weekRepositoryHomepagenpmAtom feed

Your version

2.5.0

3 Apr 2025Where it was published

2.11.13 is the newest release of 2.x.

In short

15 new21 fixed92 internal

Security

2 advisories affect 2.5.0; 2.9.14 fixes them

Release note

What's Changed

Docs

  • cli: No longer attempt to parse task name as continue value

  • Adds callout for installation instructions for PNPM

  • boundaries: Package name as tag punning

  • Workspace root microsyntax

  • turbo json: Make with public

eslint

  • eslint-config-turbo module export

  • Mark type of flat config export to satisfy Linter.Config

  • eslint: Array type lints

@turbo/repository

  • affected_packages's optimization flow

Examples

  • Unexpected top-level property default in base.js eslint config

Changelog

  • process: Differentiate between child interruption and killing

  • @turbo/repository: Revert "chore(deps): update git2 to 0.20.0"

  • process: Revert "feat(process): differentiate between child interruption and killing"

  • boundaries: Support tsconfig path aliases

  • query: Add schema flag

  • Filter logic

  • ls: Add package path to ls

  • packages: No longer match versionless packages

  • engine: No longer error if provided task is omitted by filter

  • Add JSONC support

  • clone: Turbo clone

  • Correctly forward passthrough arguments when using pkg#task format

  • boundaries: Support import attributes

  • boundaries: Unnecessary tsconfig warnings

  • affected: Consider turbo.jsonc as a default global dependency

  • prune: Support copying turbo.jsonc

  • boundaries: Implicit dependencies

  • process: Distinguish between signals used to kill children

  • boundaries: Auto ignore

  • bun: Properly handle bun lockfile keys

  • bun: Bun prune support

  • boundaries: Package rules

  • Update env variables supported by nitro

  • turbo_json: Avoid workspace validation errors

  • bun: Deserialize correctly and use optionalPeers

  • tui: Bump default scrollback length

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.