Packages

turbo

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

Upgrading turbo From 1.13.0 to 1.13.4

4 releases in betweenevery note read

Other targets from 1.13.0Clears its 2 advisories2.9.14Latest2.11.13
0
changes to make
0
advisories fixed
25
new
29
fixes

Security

2 advisories still affect 1.13.4

Upgrading to 2.9.14 clears them.

Release by release

  1. 1.13.4

    4 Jun 20249 new · 14 fixes
    • New

      turbo-ignore: don’t fail on single package repos

    • New

      Turborepo: Be explicit about which binary we failed to find

    • New

      Turborepo: Add support for $TURBO_DEFAULT$ to file hash watcher

    • New

      turborepo: Using file hashing for package watching

  2. 1.13.3

    25 Apr 202410 new · 7 fixes
    • New

      Use @repo/ pattern in math-helpers example, consistent with "getting started" and starter repo

    • New

      turbo-ignore: Usage metrics

    • New

      telemetry: Defensive config loading

    • New

      Turborepo: Flag on daemon package discovery

  3. 1.13.2nothing new or fixed in the note

  4. 1.13.1

    1 Apr 20246 new · 8 fixes
    • New

      ui: Persist logs on failure

    • New

      Turborepo: Handle package manager changes

    • New

      ui: Add ability to scroll task output

    • New

      ui: Persist all logs

3 other lines we could not sort, mostly version bumps
  • Remove async-trait from a few crates

    1.13.4
  • Yield a different warning when the cache upload times out

    1.13.4
  • Update lockfile for compatibility with next.js

    1.13.3

29 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.