← ← Back to all products
All badges & lifecycle API →
GerritEnd of Life (EOL) Dates & Support Status
Active
DevOps & CI/CDLatest Version: 3.14.4Latest Release: Sep 23, 2026
Gerrit is a free, web-based code review tool for Git repositories, used widely in open-source projects.
Support summary
Gerrit currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
3
0 lts
Versions
19
Latest Version
3.14.4
Active Support
3
EOL
16
Lifecycle Timeline
Dec 6, 2021As of Sep 27, 2026
3.14Active · Date not announced
3.13Active · Date not announced
3.12Active · Date not announced
3.11EOL · May 15, 2026
3.10EOL · Nov 10, 2025
3.9EOL · May 19, 2025
3.8EOL · Dec 2, 2024
3.7EOL · May 17, 2024
3.6EOL · Nov 25, 2023
3.5EOL · May 19, 2023
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 3.14 | May 15, 2026 | Maintained | Date not announced | 3.14.4 | No | Active |
| 3.13 | Nov 10, 2025 | Maintained | Date not announced | 3.13.10 | No | Active |
| 3.12 | May 19, 2025 | Maintained | Date not announced | 3.12.11 | No | Active |
| 3.11 | Dec 2, 2024 | Ended | May 15, 2026 | 3.11.11 | No | EOL |
| 3.10 | May 17, 2024 | Ended | Nov 10, 2025 | 3.10.9 | No | EOL |
| 3.9 | Nov 25, 2023 | Ended | May 19, 2025 | 3.9.11 | No | EOL |
| 3.8 | May 19, 2023 | Ended | Dec 2, 2024 | 3.8.10 | No | EOL |
| 3.7 | Nov 9, 2022 | Ended | May 17, 2024 | 3.7.9 | No | EOL |
| 3.6 | May 23, 2022 | Ended | Nov 25, 2023 | 3.6.8 | No | EOL |
| 3.5 | Dec 6, 2021 | Ended | May 19, 2023 | 3.5.6 | No | EOL |
| 3.4 | May 17, 2021 | Ended | Nov 9, 2022 | 3.4.8 | No | EOL |
| 3.3 | Dec 1, 2020 | Ended | May 24, 2022 | 3.3.11 | No | EOL |
| 3.2 | Jun 1, 2020 | Ended | Dec 7, 2021 | 3.2.14 | No | EOL |
| 3.1 | Nov 14, 2019 | Ended | May 19, 2021 | 3.1.16 | No | EOL |
| 3.0 | May 15, 2019 | Ended | Dec 1, 2020 | 3.0.16 | No | EOL |
| 2.16 | Nov 15, 2018 | Ended | Jun 1, 2020 | 2.16.28 | No | EOL |
| 2.15 | Mar 28, 2018 | Ended | Nov 15, 2019 | 2.15.22 | No | EOL |
| 2.14 | Apr 26, 2017 | Ended | May 31, 2019 | 2.14.22 | No | EOL |
| 2.13 | Sep 21, 2016 | Ended | Ended; date not announced | 2.13.14 | No | EOL |
Data sources
Embed this badge
Show Gerrit's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/gerrit/)HTML
<a href="https://eol.wiki/gerrit/"><img src="https://eol.wiki/badge/gerrit.svg" alt="Gerrit end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Gerrit have reached end of life?
The following Gerrit versions have reached end of life and no longer receive security updates: 3.11, 3.10, 3.9, 3.8, 3.7, 3.6, 3.5, 3.4 (and 8 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Gerrit 3.11?
Gerrit 3.11 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Gerrit?
The latest version of Gerrit is 3.14.4, released in the 3.14 release cycle.
How many versions of Gerrit are currently supported?
Gerrit currently has 3 actively supported version(s): 3.14, 3.13, 3.12.
When does Gerrit 3.14 reach end of life?
Gerrit 3.14 does not have a specific end-of-life date announced yet.
What should I do when Gerrit reaches end of life?
When a Gerrit version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.