← ← Back to all products
Turborepo
Active
Tools & MonitoringLatest Version: 2.9.18Latest Release: Jun 10, 2026
Turborepo is a high-performance build system for JavaScript and TypeScript monorepos, written in Rust and maintained by Vercel. Only the latest major line receives active maintenance.
Support summary
Turborepo currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
1
0 lts
Versions
2
Latest Version
2.9.18
Active Support
1
EOL
1
Lifecycle Timeline
Today ↓
2
2
1
1
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2 | Jun 4, 2024 | Yes | No | 2.9.18 | No | Active |
| 1 | Dec 9, 2021 | No | Yes | 1.13.4 | No | EOL |
Data sources
Sources
Last verified
Jun 24, 2026
Community-maintained lifecycle data. Verify against official release notes before production migration.
Frequently Asked Questions
Which versions of Turborepo have reached end of life?
The following Turborepo versions have reached end of life and no longer receive security updates: 1. It is recommended to upgrade to a supported version.
Is it safe to continue using Turborepo 1?
Turborepo 1 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Turborepo?
The latest version of Turborepo is 2.9.18, released in the 2 release cycle.
How many versions of Turborepo are currently supported?
Turborepo currently has 1 actively supported version(s): 2.
When does Turborepo 2 reach end of life?
Turborepo 2 does not have a specific end-of-life date announced yet.
What should I do when Turborepo reaches end of life?
When a Turborepo version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.