Gitlab Runner End of Life Dates
other
Developers rely on continuous integration and continuous deployment tools to streamline their workflow, and Gitlab Runner plays a crucial role in this process. Created to facilitate automated testing and deployment, Gitlab Runner has been maintained by Gitlab, a renowned provider of development tools. Since its inception, the tool has gained popularity among developers due to its ability to simplify complex workflows and enhance productivity. With a focus on flexibility and customization, Gitlab Runner has become an essential component of many development pipelines.
The end-of-life landscape for Gitlab Runner reveals that out of 15 total versions, 12 have already reached their end-of-life, leaving only 3 active versions. The latest stable version, 19.2.0, is the current benchmark for developers. However, version 19.0 is next in line to expire, with its end-of-life date set for August 20, 2026. This follows the recent expiration of version 18.11 on July 16, 2026. As the number of active versions dwindles, developers must stay vigilant and plan their updates accordingly to avoid potential disruptions.
Despite the absence of tracked CVEs, developers should remain cautious and proactive in maintaining their Gitlab Runner installations. With no critical vulnerabilities reported, the security landscape appears stable, but this can change rapidly. Given the lack of known vulnerabilities, there is no most affected version to report. Furthermore, with no known vulnerabilities, there is no applicable KEV status. To ensure continued security and compatibility, developers should prioritize updating to the latest stable version, 19.2.0, and closely monitor the end-of-life schedule to avoid any potential security risks or compatibility issues that may arise in the future.
Last updated: Jul 28, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 19.2 | Jul 16, 2026 | Aug 20, 2026 | Oct 20, 2026 | in 84d | 19.2.0 | — | EOL soon | |
| 19.1 | Jun 18, 2026 | Jul 16, 2026 | Sep 17, 2026 | in 51d | 19.1.1 | — | EOL soon | |
| 19.0 | May 21, 2026 | Jun 18, 2026 | Aug 20, 2026 | in 23d | 19.0.2 | — | EOL soon | |
| 18.11 | Apr 16, 2026 | May 21, 2026 | Jul 16, 2026 | 12d ago | 18.11.4 | — | EOL | |
| 18.10 | Mar 19, 2026 | Apr 16, 2026 | Jun 18, 2026 | 40d ago | 18.10.1 | — | EOL | |
| 18.9 | Feb 19, 2026 | Mar 19, 2026 | May 21, 2026 | 68d ago | 18.9.0 | — | EOL | |
| 18.8 | Jan 15, 2026 | Feb 19, 2026 | Apr 16, 2026 | 103d ago | 18.8.0 | — | EOL | |
| 18.7 | Dec 18, 2025 | Jan 15, 2026 | Mar 19, 2026 | 131d ago | 18.7.2 | — | EOL | |
| 18.6 | Nov 20, 2025 | Dec 18, 2025 | Feb 19, 2026 | 159d ago | 18.6.6 | — | EOL | |
| 18.5 | Oct 16, 2025 | Nov 20, 2025 | Jan 15, 2026 | 194d ago | 18.5.0 | — | EOL | |
| 18.4 | Sep 18, 2025 | Oct 16, 2025 | Dec 18, 2025 | 222d ago | 18.4.0 | — | EOL | |
| 18.3 | Aug 21, 2025 | Sep 18, 2025 | Nov 20, 2025 | 250d ago | 18.3.1 | — | EOL | |
| 18.2 | Jul 16, 2025 | Aug 21, 2025 | Oct 16, 2025 | 285d ago | 18.2.2 | — | EOL | |
| 18.1 | Jun 18, 2025 | Jul 16, 2025 | Sep 18, 2025 | 313d ago | 18.1.3 | — | EOL | |
| 18.0 | May 14, 2025 | Jun 18, 2025 | Aug 21, 2025 | 341d ago | 18.0.5 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
