Tarantool End of Life Dates
other
Developers rely on Tarantool for its robust capabilities, and to ensure seamless operations, it's essential to stay informed about its lifecycle. Created to address the need for efficient data management, Tarantool has been maintained by its dedicated community since its inception. The community's efforts have made Tarantool a go-to solution for many, with its ability to track end-of-life dates, supported versions, and security patch timelines being a significant factor in its adoption. By knowing when each Tarantool release reaches end of support, developers can plan their upgrades accordingly, minimizing potential disruptions and security risks.
The current landscape of Tarantool's versions reveals a total of 18 releases, with 11 of them having already reached their end-of-life. Currently, 7 versions remain active, providing developers with a range of options. The latest stable version, 2.11.9, is the most recent addition to this lineup. Looking ahead, version 3.2 is slated to reach its end-of-life on 2026-08-26, marking an important milestone for developers who are currently utilizing this version. This knowledge allows them to prepare for the transition to a supported version, ensuring continuity and security. The last end-of-life date was 2024-08-26 for version 3.1, demonstrating the ongoing evolution of Tarantool's lifecycle.
The security outlook for Tarantool is notably positive, with a total of 0 CVEs tracked and 0 critical CVEs reported. As a result, there is no most affected version, underscoring the robust security posture of Tarantool. This favorable security picture is a testament to the community's dedication to maintaining the product's integrity. Given this context, developers should remain vigilant and continue to monitor the lifecycle of their Tarantool versions, taking proactive steps to upgrade to supported versions as necessary to maintain the security and reliability of their applications.
Last updated: Sep 7, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 3.8 | Jul 10, 2026 | — | No | — | 3.8.1 | — | Active | |
| 3.7 | Apr 22, 2026 | — | No | — | 3.7.1 | — | Active | |
| 3.6 | Dec 12, 2025 | — | No | — | 3.6.4 | — | Active | |
| 3.5 | Aug 27, 2025 | — | No | — | 3.5.2 | — | Active | |
| 3.4 | Apr 15, 2025 | — | Apr 14, 2027 | in 219d | 3.4.2 | — | Active | |
| 3.3 | Nov 29, 2024 | — | Nov 29, 2026 | in 83d | 3.3.5 | — | EOL soon | |
| 3.2 | Aug 26, 2024 | — | Aug 26, 2026 | 12d ago | 3.2.4 | — | EOL | |
| 3.1 | Apr 16, 2024 | — | Aug 26, 2024 | 742d ago | 3.1.2 | — | EOL | |
| 3.0 | Dec 26, 2023 | — | Apr 16, 2024 | 874d ago | 3.0.2 | — | EOL | |
| 2.11 LTS | May 24, 2023 | — | May 24, 2027 | in 259d | 2.11.9 | — | Active | |
| 2.10 | May 22, 2022 | — | Sep 14, 2023 | 1089d ago | 2.10.8 | — | EOL | |
| 2.8 | Dec 30, 2020 | — | Apr 25, 2022 | 1596d ago | 2.8.4 | — | EOL | |
| 2.7 | Oct 23, 2020 | — | Aug 19, 2021 | 1845d ago | 2.7.3 | — | EOL | |
| 2.6 | Jul 17, 2020 | — | Apr 21, 2021 | 1965d ago | 2.6.3 | — | EOL | |
| 2.5 | Apr 20, 2020 | — | Dec 30, 2020 | 2077d ago | 2.5.3 | — | EOL | |
| 2.4 | Jan 10, 2020 | — | Oct 23, 2020 | 2145d ago | 2.4.3 | — | EOL | |
| 2.3 | Aug 2, 2019 | — | Jul 17, 2020 | 2243d ago | 2.3.3 | — | EOL | |
| 2.2 | Mar 22, 2019 | — | Apr 20, 2020 | 2331d ago | 2.2.3 | — | EOL | |
| 1.10 LTS | Mar 7, 2018 | — | May 24, 2023 | 1202d ago | 1.10.15 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
