Alibaba Ack End of Life Dates
other
Developers rely on accurate and timely information to manage their software portfolios, and tracking end-of-life dates is a critical aspect of this process. Alibaba Ack, a tool created to facilitate this task, has been maintained by its development team since its inception. The primary goal of Alibaba Ack is to provide a centralized platform for tracking supported versions and security patch timelines, enabling developers to plan upgrades and ensure continuity. By leveraging Alibaba Ack, developers can stay informed about upcoming end-of-life dates and make informed decisions about their software investments.
The landscape of Alibaba Ack versions is characterized by a total of 14 releases, with 12 of these versions having already reached their end-of-life. Currently, only 2 versions remain active, and developers should be aware of the impending end-of-life date for version 1.30, which is scheduled to expire on 2026-06-30. This information is crucial for planning purposes, as it allows developers to allocate resources and prioritize upgrades accordingly. The most recent end-of-life date was 2026-05-31, when version 1.33 reached the end of its support period. By staying up-to-date with this information, developers can minimize disruptions and ensure a smooth transition to supported versions.
From a security perspective, Alibaba Ack has a pristine record, with a total of 0 tracked CVEs and 0 critical vulnerabilities. As a result, there is no most affected version, and the KEV status is not applicable in this case. Given the absence of known security vulnerabilities, developers can focus on planning upgrades and migrations to ensure continuity and support. However, it is essential to continue monitoring the security landscape and stay informed about any potential issues that may arise. By doing so, developers can proactively address any security concerns and maintain the integrity of their software portfolios.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 1.34 | Sep 30, 2025 | — | Sep 30, 2026 | in 68d | — | — | EOL soon | |
| 1.33 | May 31, 2025 | — | May 31, 2026 | 54d ago | — | — | EOL | |
| 1.32 | Jan 31, 2025 | — | Jan 31, 2026 | 174d ago | — | — | EOL | |
| 1.31 | Sep 30, 2024 | — | Sep 30, 2025 | 297d ago | — | — | EOL | |
| 1.30 | Jun 30, 2024 | — | Jun 30, 2026 | 24d ago | — | — | EOL | |
| 1.28 | Oct 31, 2023 | — | Oct 31, 2025 | 266d ago | — | — | EOL | |
| 1.26 | Apr 30, 2023 | — | Apr 30, 2025 | 450d ago | — | — | EOL | |
| 1.24 | Sep 30, 2022 | — | Sep 30, 2024 | 662d ago | — | — | EOL | |
| 1.22 | Dec 31, 2021 | — | Oct 31, 2023 | 997d ago | — | — | EOL | |
| 1.20 | Apr 30, 2021 | — | Apr 30, 2023 | 1181d ago | — | — | EOL | |
| 1.18 | Sep 30, 2020 | — | Sep 30, 2022 | 1393d ago | — | — | EOL | |
| 1.16 | Feb 29, 2020 | — | Jun 30, 2022 | 1485d ago | — | — | EOL | |
| 1.14 | Aug 31, 2019 | — | Jul 31, 2021 | 1819d ago | — | — | EOL | |
| 1.12 | Mar 31, 2019 | — | Dec 31, 2020 | 2031d ago | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
