Coder End of Life Dates

other

Developers rely on skilled professionals to create and maintain the complex systems that power their applications, and these individuals are often referred to as coders. A coder is essentially an author of computer source code, possessing a high level of skill in computer programming. This expertise is essential for jobs that require software development and engineering, and the titles software developer and software engineer are frequently used to describe these roles. The profession has been around since the inception of computer programming, with the first programmer being credited to have emerged in the mid-20th century. The upkeep of this profession is maintained by various educational institutions and professional organizations that provide training and certification programs for aspiring coders.

The end-of-life landscape for coders is relatively straightforward, with a total of 28 distinct versions, 25 of which are no longer supported. The latest stable version, 2.32.6, is one of the three active versions currently in use. Recently, version 2.31 reached its end-of-life date on 2026-06-02, marking the latest milestone in the profession's evolution. With no announced date for the next version to expire, developers can continue to work with the current active versions without immediate concern for upcoming end-of-life transitions.

From a security perspective, coders do not pose a significant risk, as there are no known Common Vulnerabilities and Exposures (CVEs) associated with them. This means that there are no critical CVEs to report, and no specific version is more affected than others. As a result, developers do not need to take any specific action to mitigate potential security risks related to coders. The lack of CVEs also means that coders are not subject to the Known Exploited Vulnerabilities (KEV) catalog, which further reduces the security concerns surrounding this profession. Overall, the security picture for coders is extremely favorable, allowing developers to focus on their work without worrying about potential vulnerabilities.

Last updated: Sep 7, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
2.37 Sep 1, 2026No2.37.0Active
2.36 Aug 4, 2026No2.36.4Active
2.35 Jul 7, 2026Sep 1, 2026No2.35.7Active
2.34 LTSJun 2, 2026Aug 4, 2026Sep 1, 20266d ago2.34.10EOL
2.33 May 6, 2026Jul 7, 2026Aug 4, 202634d ago2.33.11EOL
2.32 Apr 14, 2026Jun 2, 2026Jul 7, 202662d ago2.32.10EOL
2.31 Mar 3, 2026May 6, 2026Jun 2, 202697d ago2.31.14EOL
2.30 Feb 3, 2026Apr 14, 2026May 6, 2026124d ago2.30.9EOL
2.29 LTSDec 2, 2025Feb 23, 2026Apr 14, 2026146d ago2.29.19EOL
2.28 Nov 4, 2025Feb 3, 2026Feb 23, 2026196d ago2.28.11EOL
2.27 Oct 7, 2025Dec 2, 2025Feb 3, 2026216d ago2.27.11EOL
2.26 Sep 3, 2025Nov 4, 2025Dec 2, 2025279d ago2.26.6EOL
2.25 Aug 5, 2025Oct 7, 2025Nov 4, 2025307d ago2.25.3EOL
2.24 LTSJul 1, 2025Sep 3, 2025Oct 7, 2025335d ago2.24.6EOL
2.23 Jun 3, 2025Aug 5, 2025Sep 3, 2025369d ago2.23.5EOL
2.22 May 16, 2025Jul 1, 2025Aug 5, 2025398d ago2.22.1EOL
2.21 Apr 1, 2025Jun 3, 2025Jul 1, 2025433d ago2.21.3EOL
2.20 Mar 5, 2025May 16, 2025Jun 3, 2025461d ago2.20.3EOL
2.19 Feb 4, 2025Apr 1, 2025May 16, 2025479d ago2.19.3EOL
2.18 Dec 3, 2024Mar 5, 2025Apr 1, 2025524d ago2.18.5EOL
2.17 Nov 5, 2024Feb 4, 2025Mar 5, 2025551d ago2.17.3EOL
2.16 Oct 1, 2024Dec 3, 2024Feb 4, 2025580d ago2.16.1EOL
2.15 Sep 3, 2024Nov 5, 2024Dec 3, 2024643d ago2.15.4EOL
2.14 Aug 6, 2024Oct 1, 2024Nov 5, 2024671d ago2.14.4EOL
2.13 Jul 2, 2024Sep 3, 2024Oct 1, 2024706d ago2.13.5EOL
2.12 Jun 4, 2024Aug 6, 2024Sep 3, 2024734d ago2.12.6EOL
2.11 May 7, 2024Jul 2, 2024Aug 6, 2024762d ago2.11.4EOL
2.10 Apr 3, 2024Jun 4, 2024Jul 2, 2024797d ago2.10.3EOL
2.9 Mar 7, 2024May 7, 2024Jun 4, 2024825d ago2.9.4EOL
2.8 Feb 6, 2024Apr 3, 2024May 7, 2024853d ago2.8.5EOL
2.7 Jan 1, 2024Mar 7, 2024Apr 3, 2024887d ago2.7.3EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions