Support policy

Package managers

Core turbo functionality depends on the package managers in the JavaScript ecosystem and their implementations of Workspaces and lockfiles formats.

Platforms

turbo is generally supported on Debian-based Linux distributions, macOS, and Windows on both x86_64 and ARM 64 architectures. Specifically, we build and ship the following binaries via npm:

• turbo-darwin-64 (macOS with Intel chips)
• turbo-darwin-arm64 (macOS with Apple Silicon)
• turbo-linux-64
• turbo-linux-arm64
• turbo-windows-64 ¹
• turbo-windows-arm64 ¹

Node.js

Core turbo functionality does not depend on the active Node.js version on your system, but some packages in the Turborepo ecosystem such as create-turbo, turbo-ignore, and eslint-config-turbo do. For these features, we intend to support the Active and Maintenance LTS versions of Node.js.

Turborepo's examples are also expected to work with these Node.js versions.

Version control

We support repositories that are version controlled with Git and repositories that don't have version control at all. Any other version control system will be ignored.

Note that we use Git to hash files, so repositories without git may perform and behave differently.

LTS policy

Major versions of Turborepo will be supported for two years from the release date of the next major version.

Changes required for critical security fixes in older versions will be backported. Such situations will be rare and will land as semver-minor releases, even if they are breaking changes.

We highly encourage you to use the most current version of Turborepo whenever possible.