ShutdownRadar
Support lifecycle

gitlab runner end of life dates — full support timeline

Next end of life: 2026-08-20·cycle 19.0·20 days away

12 of 15 tracked gitlab runner releases have already reached end of life. The dates below are published support dates, not estimates.

Version support timeline

ReleaseReleasedEnd of lifeLatestStatus
19.22026-07-162026-10-2019.2.1ends soon
19.12026-06-182026-09-1719.1.2ends soon
19.02026-05-212026-08-2019.0.3ends soon
18.112026-04-162026-07-1618.11.4ended
18.102026-03-192026-06-1818.10.1ended
18.92026-02-192026-05-2118.9.0ended
18.82026-01-152026-04-1618.8.0ended
18.72025-12-182026-03-1918.7.2ended
18.62025-11-202026-02-1918.6.6ended
18.52025-10-162026-01-1518.5.0ended
18.42025-09-182025-12-1818.4.0ended
18.32025-08-212025-11-2018.3.1ended
18.22025-07-162025-10-1618.2.2ended
18.12025-06-182025-09-1818.1.3ended
18.02025-05-142025-08-2118.0.5ended

Who is affected

Anyone running an unsupported gitlab runner release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.

Source

These dates are maintained by endoflife.date/gitlab-runner, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.

Get told before the next gitlab runner deadline

You are reading this because a gitlab runner release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every gitlab runner and related deadline as it is announced, with exact dates and primary sources.

Watch gitlab runner deadlines Team monitoring pilot →

Takes about twenty seconds. No account, no card, no tracking.

All upcoming deadlines · Full archive