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: Oct 7, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
19.4 Sep 17, 2026Oct 15, 2026Dec 17, 2026in 71d19.4.1—EOL soon
19.3 Aug 20, 2026Sep 17, 2026Nov 19, 2026in 43d19.3.3—EOL soon
19.2 Jul 16, 2026Aug 20, 2026Oct 15, 2026in 8d19.2.6—EOL soon
19.1 Jun 18, 2026Jul 16, 2026Sep 17, 202620d ago19.1.5—EOL
19.0 May 21, 2026Jun 18, 2026Aug 20, 202648d ago19.0.3—EOL
18.11 Apr 16, 2026May 21, 2026Jul 16, 202683d ago18.11.4—EOL
18.10 Mar 19, 2026Apr 16, 2026Jun 18, 2026111d ago18.10.1—EOL
18.9 Feb 19, 2026Mar 19, 2026May 21, 2026139d ago18.9.0—EOL
18.8 Jan 15, 2026Feb 19, 2026Apr 16, 2026174d ago18.8.0—EOL
18.7 Dec 18, 2025Jan 15, 2026Mar 19, 2026202d ago18.7.2—EOL
18.6 Nov 20, 2025Dec 18, 2025Feb 19, 2026230d ago18.6.6—EOL
18.5 Oct 16, 2025Nov 20, 2025Jan 15, 2026265d ago18.5.0—EOL
18.4 Sep 18, 2025Oct 16, 2025Dec 18, 2025293d ago18.4.0—EOL
18.3 Aug 21, 2025Sep 18, 2025Nov 20, 2025321d ago18.3.1—EOL
18.2 Jul 16, 2025Aug 21, 2025Oct 16, 2025356d ago18.2.2—EOL
18.1 Jun 18, 2025Jul 16, 2025Sep 18, 2025384d ago18.1.3—EOL
18.0 May 14, 2025Jun 18, 2025Aug 21, 2025412d ago18.0.5—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions