GitLab End of Life: Supported Versions and Dates

Last verified by Usman Khurshid · 2 of 68 versions supported · 1 recent changes

GitLab 19.5, 19.4 and 19.3 are the only self-managed versions getting security fixes right now, and only 19.5 still gets bug fixes. 19.3 drops out when GitLab 19.6 comes out on 19 November 2026. Every version from 19.2 back is unsupported.

Security fixes only

1 mo left

GitLab 19.5 gets security fixes only, until 21 Jan 2027 (1 mo left). Bug fixes ended on 19 Nov 2026. This date is our estimate: GitLab backports security fixes to the current and two previous monthly releases, and minors ship on the third Thursday of each month, so bug fixes end when the next minor ships (19 November 2026); security fixes end when the third minor after this one ships (21 January 2027).

GitLab releases a new minor version on the third Thursday of every month. The current release gets bug fixes, and security fixes are backported to the current release and the two before it. So each minor version gets security fixes for about three months, and there are no LTS releases.

Patch releases come out twice a month, on the Wednesdays the week before and the week after each monthly release. Major versions arrive each May, when deprecated features are removed. GitLab 20.0 is scheduled for 20 May 2027.

These dates apply to self-managed GitLab (Omnibus packages, Helm charts and Docker images). GitLab.com always runs the latest code. For finished versions, the end date is the release date of the version that replaced it. For supported versions it is the scheduled release date, marked as estimated.

GitLab support dates

VersionReleasedBug fixesSecurity fixes untilTime leftStatusLatest
GitLab 19.5Estimated[1]Estimated[1]1 mo leftSecurity fixes only19.5.4
GitLab 19.4Confirmed[1]Estimated[1]0 mo leftSecurity fixes only19.4.6
GitLab 19.3Confirmed[1]Estimated[1]EndedUnsupported19.3.8
GitLab 19.2Confirmed[1]Confirmed[1]EndedUnsupported19.2.10
GitLab 19.1Confirmed[1]Confirmed[1]EndedUnsupported19.1.10
GitLab 19.0Confirmed[1]Confirmed[1]EndedUnsupported19.0.11
GitLab 18.11Confirmed[1]Confirmed[1]EndedUnsupported18.11.14
GitLab 18.10Confirmed[1]Confirmed[1]EndedUnsupported18.10.8
GitLab 18.9Confirmed[1]Confirmed[1]EndedUnsupported18.9.8
GitLab 18.8Confirmed[1]Confirmed[1]EndedUnsupported18.8.11
GitLab 18.7Confirmed[1]Confirmed[1]EndedUnsupported18.7.7
GitLab 18.6Confirmed[1]Confirmed[1]EndedUnsupported18.6.8
GitLab 18.5Confirmed[1]Confirmed[1]EndedUnsupported18.5.7
GitLab 18.4Confirmed[1]Confirmed[1]EndedUnsupported18.4.6
GitLab 18.3Confirmed[1]Confirmed[1]EndedUnsupported18.3.6
GitLab 18.2Confirmed[1]Confirmed[1]EndedUnsupported18.2.8
GitLab 18.1Confirmed[1]Confirmed[1]EndedUnsupported18.1.6
GitLab 18.0Confirmed[1]Confirmed[1]EndedUnsupported18.0.6
GitLab 17.11Confirmed[1]Confirmed[1]EndedUnsupported17.11.7
GitLab 17.10Confirmed[1]Confirmed[1]EndedUnsupported17.10.8
GitLab 17.9Confirmed[1]Confirmed[1]EndedUnsupported17.9.8
GitLab 17.8Confirmed[1]Confirmed[1]EndedUnsupported17.8.7
GitLab 17.7Confirmed[1]Confirmed[1]EndedUnsupported17.7.7
GitLab 17.6Confirmed[1]Confirmed[1]EndedUnsupported17.6.5
GitLab 17.5EndedUnsupported
GitLab 17.4EndedUnsupported
GitLab 17.3EndedUnsupported
GitLab 17.2EndedUnsupported
GitLab 17.1EndedUnsupported
GitLab 17.0EndedUnsupported
GitLab 16.11EndedUnsupported16.11.10
GitLab 16.10EndedUnsupported
GitLab 16.9EndedUnsupported
GitLab 16.8EndedUnsupported
GitLab 16.7EndedUnsupported
GitLab 16.6EndedUnsupported
GitLab 16.5EndedUnsupported
GitLab 16.4EndedUnsupported
GitLab 16.3EndedUnsupported
GitLab 16.2EndedUnsupported
GitLab 16.1EndedUnsupported
GitLab 16.0EndedUnsupported
GitLab 15.11EndedUnsupported15.11.13
GitLab 15.10EndedUnsupported
GitLab 15.9EndedUnsupported
GitLab 15.8EndedUnsupported
GitLab 15.7EndedUnsupported
GitLab 15.6EndedUnsupported
GitLab 15.5EndedUnsupported
GitLab 15.4EndedUnsupported
GitLab 15.3EndedUnsupported
GitLab 15.2EndedUnsupported
GitLab 15.1EndedUnsupported
GitLab 15.0EndedUnsupported
GitLab 14.10EndedUnsupported14.10.5
GitLab 14.9EndedUnsupported
GitLab 14.8EndedUnsupported
GitLab 14.7EndedUnsupported
GitLab 14.6EndedUnsupported
GitLab 14.5EndedUnsupported
GitLab 14.4EndedUnsupported
GitLab 14.3EndedUnsupported
GitLab 14.2EndedUnsupported
GitLab 14.1EndedUnsupported
GitLab 14.0EndedUnsupported
GitLab 13.12EndedUnsupported13.12.15
GitLab 13.11EndedUnsupported
GitLab 13.10EndedUnsupported

Official published by the vendor · Confirmed observed (for example, patches stopped) · Estimated our forecast, with the rule stated · How we date things

Timeline

2025202620272028GitLab 19.5GitLab 19.5: 15 Oct 2026 to 21 Jan 2027GitLab 19.4GitLab 19.4: 17 Sep 2026 to 17 Dec 2026GitLab 19.3GitLab 19.3: 20 Aug 2026 to 19 Nov 2026GitLab 19.2GitLab 19.2: 16 Jul 2026 to 15 Oct 2026GitLab 19.1GitLab 19.1: 18 Jun 2026 to 17 Sep 2026GitLab 19.0GitLab 19.0: 21 May 2026 to 20 Aug 2026GitLab 18.11GitLab 18.11: 16 Apr 2026 to 16 Jul 2026GitLab 18.10GitLab 18.10: 19 Mar 2026 to 18 Jun 2026GitLab 18.9GitLab 18.9: 19 Feb 2026 to 21 May 2026GitLab 18.8GitLab 18.8: 15 Jan 2026 to 16 Apr 2026GitLab 18.7GitLab 18.7: 18 Dec 2025 to 19 Mar 2026GitLab 18.6GitLab 18.6: 20 Nov 2025 to 19 Feb 2026GitLab 18.5GitLab 18.5: 16 Oct 2025 to 15 Jan 2026GitLab 18.4GitLab 18.4: 18 Sep 2025 to 18 Dec 2025today

Bug fixesSecurity fixes untilExtended supportEstimatedEnded

What happens when support ends

Will it still run?

Your GitLab instance keeps running. Repositories, CI/CD pipelines and users are not affected on the date itself.

Will it get security fixes?

GitLab stops including that minor version in its patch releases. GitLab ships security fixes in patch releases every two weeks, so an unsupported instance falls behind quickly.

What stops working?

The further behind you are, the longer the upgrade. GitLab requires upgrade stops at certain versions, so you can't jump straight from an old version to the latest. GitLab's documentation says the GitLab Runner major.minor version should stay in sync with the GitLab version, so an old instance holds back Runner upgrades too.

What are my options?

  • Upgrade to the latest 19.x patch release. Use the GitLab Upgrade Path tool to find the required stops.
  • Plan to upgrade every month, or at least every quarter, to stay inside the three-release security window.
  • Move to GitLab.com or GitLab Dedicated if you can't keep up with self-managed upgrades.

What to do

Check your version on the instance's /help page, or on the server run sudo gitlab-rake gitlab:env:info (Linux package) or cat /opt/gitlab/embedded/service/gitlab-rails/VERSION.

Before upgrading, put your current and target versions into the GitLab Upgrade Path tool (gitlab-com.gitlab.io/support/toolbox/upgrade-path) and upgrade through each required stop. Take a backup with sudo gitlab-backup create first.

GitLab versions: end of support, one by one

GitLab 19.5 end of life Security fixes only

GitLab 19.5 gets security fixes only, until 21 Jan 2027 (1 mo left). Bug fixes ended on 19 Nov 2026. This date is our estimate: GitLab backports security fixes to the current and two previous monthly releases, and minors ship on the third Thursday of each month, so bug fixes end when the next minor ships (19 November 2026); security fixes end when the third minor after this one ships (21 January 2027).

GitLab 19.4 end of life Security fixes only

GitLab 19.4 gets security fixes only, until 17 Dec 2026 (0 mo left). Bug fixes ended on 15 Oct 2026. This date is our estimate: GitLab backports security fixes to the current and two previous monthly releases, and minors ship on the third Thursday of each month, so security fixes end when the third minor after this one ships (17 December 2026).

GitLab 19.3 end of life Unsupported

GitLab 19.3 stopped getting security updates on 19 Nov 2026 and is no longer supported. This date is our estimate: GitLab backports security fixes to the current and two previous monthly releases, and minors ship on the third Thursday of each month, so security fixes end when the third minor after this one ships (19 November 2026).

GitLab 19.2 end of life Unsupported

GitLab 19.2 stopped getting security updates on 15 Oct 2026 and is no longer supported.

GitLab 19.1 end of life Unsupported

GitLab 19.1 stopped getting security updates on 17 Sep 2026 and is no longer supported.

GitLab 19.0 end of life Unsupported

GitLab 19.0 stopped getting security updates on 20 Aug 2026 and is no longer supported.

GitLab 18.11 end of life Unsupported

GitLab 18.11 stopped getting security updates on 16 Jul 2026 and is no longer supported.

GitLab 18.10 end of life Unsupported

GitLab 18.10 stopped getting security updates on 18 Jun 2026 and is no longer supported.

GitLab 18.9 end of life Unsupported

GitLab 18.9 stopped getting security updates on 21 May 2026 and is no longer supported.

GitLab 18.8 end of life Unsupported

GitLab 18.8 stopped getting security updates on 16 Apr 2026 and is no longer supported.

GitLab 18.7 end of life Unsupported

GitLab 18.7 stopped getting security updates on 19 Mar 2026 and is no longer supported.

GitLab 18.6 end of life Unsupported

GitLab 18.6 stopped getting security updates on 19 Feb 2026 and is no longer supported.

GitLab 18.5 end of life Unsupported

GitLab 18.5 stopped getting security updates on 15 Jan 2026 and is no longer supported.

GitLab 18.4 end of life Unsupported

GitLab 18.4 stopped getting security updates on 18 Dec 2025 and is no longer supported.

GitLab 18.3 end of life Unsupported

GitLab 18.3 stopped getting security updates on 20 Nov 2025 and is no longer supported.

GitLab 18.2 end of life Unsupported

GitLab 18.2 stopped getting security updates on 16 Oct 2025 and is no longer supported.

GitLab 18.1 end of life Unsupported

GitLab 18.1 stopped getting security updates on 18 Sep 2025 and is no longer supported.

GitLab 18.0 end of life Unsupported

GitLab 18.0 stopped getting security updates on 21 Aug 2025 and is no longer supported.

GitLab 17.11 end of life Unsupported

GitLab 17.11 stopped getting security updates on 17 Jul 2025 and is no longer supported.

GitLab 17.10 end of life Unsupported

GitLab 17.10 stopped getting security updates on 19 Jun 2025 and is no longer supported.

For businesses and auditors

Paste this into a risk register, an audit response or an insurance questionnaire. It updates with the version picked above.

As of 22 Nov 2026: GitLab 19.5 gets security fixes only, until 21 Jan 2027 (1 mo left). Bug fixes ended on 19 Nov 2026. This date is our estimate: GitLab backports security fixes to the current and two previous monthly releases, and minors ship on the third Thursday of each month, so bug fixes end when the next minor ships (19 November 2026); security fixes end when the third minor after this one ships (21 January 2027). Source: https://www.itechtics.com/eol/gitlab/, verified 11 Nov 2026.

Get GitLab end-of-life alerts

We email you 90, 30 and 7 days before a GitLab version loses support, and when a vendor moves a date. One email at most per day, unsubscribe in one click.

Prefer your calendar? Add GitLab end dates to your calendar (subscribe to the link in Outlook, Google or Apple Calendar).

GitLab support policy

GitLab backports bug fixes to the current stable release only, and security fixes to the current release and the previous two monthly releases. Minor releases ship on the third Thursday of each month, and major releases each May.

What changed

  • GitLab 19.3 reached end of support.
  • GitLab 18.8 · Name: (empty) → GitLab 18.8
  • GitLab 19.5 was released.
  • GitLab 19.2 reached end of support.
  • GitLab 19.4 was released.
  • GitLab 19.1 reached end of support.
  • GitLab 19.3 was released.
  • GitLab 19.0 reached end of support.
  • GitLab 19.2 was released.
  • GitLab 18.11 reached end of support.

Frequently asked questions

Which GitLab versions are still supported?

As of 22 Nov 2026, these GitLab versions get security updates: GitLab 19.5, GitLab 19.4.

When does GitLab 19.5 support end?

GitLab 19.5 gets security fixes only, until 21 Jan 2027 (1 mo left). Bug fixes ended on 19 Nov 2026. This date is our estimate: GitLab backports security fixes to the current and two previous monthly releases, and minors ship on the third Thursday of each month, so bug fixes end when the next minor ships (19 November 2026); security fixes end when the third minor after this one ships (21 January 2027).

What happens when GitLab reaches end of life?

Your GitLab instance keeps running. Repositories, CI/CD pipelines and users are not affected on the date itself. GitLab stops including that minor version in its patch releases. GitLab ships security fixes in patch releases every two weeks, so an unsupported instance falls behind quickly.

Which GitLab versions are supported?

As of 11 November 2026, security fixes go to 19.5, 19.4 and 19.3, and bug fixes only to 19.5. After 19.6 ships on 19 November 2026, the supported versions will be 19.6, 19.5 and 19.4.

Is GitLab 18.11 still supported?

No. 18.11 was the last 18.x release. Its security support ended when 19.2 came out on 16 July 2026, and GitLab released a few more patches for it until October 2026.

How long is a GitLab version supported?

About three months of security fixes, because GitLab patches the current release and the two before it. Bug fixes cover only the current month's release.

Does GitLab have an LTS version?

No. Self-managed GitLab has no long-term support release. You need to upgrade regularly to keep getting security fixes.

When is GitLab 20.0 released?

GitLab's maintenance policy schedules 20.0 for 20 May 2027.

Sources and method

  1. docs.gitlab.com/policy/maintenance/
  2. GitLab maintenance policy
  3. GitLab release posts
  4. GitLab tags (patch versions)

Dates come from the vendor's own lifecycle pages wherever they exist and are checked against them on a schedule. A date is Official when the vendor publishes it, Confirmed when we have seen the updates stop, and Estimated when the vendor publishes nothing and we forecast it from their past behaviour. The rule is shown next to every estimate. Status and time left are worked out from today's date.

Spotted a wrong date? Tell us and include the source.