← ← Back to all products
All badges & lifecycle API →
Apache SubversionEnd of Life (EOL) Dates & Support Status
Active
Tools & MonitoringLatest Version: 1.14.5Latest Release: Dec 8, 2024
Apache Subversion (SVN) is a centralized version control system for tracking changes in files and directories.
Support summary
Apache Subversion 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
1
12 lts
Versions
15
Latest Version
1.14.5
Active Support
1
EOL
14
Lifecycle Timeline
Jun 19, 2008As of Sep 27, 2026
1.14Active · Date not announced
1.13EOL · Ended; date not announced
1.12EOL · Ended; date not announced
1.11EOL · Ended; date not announced
1.10EOL · Ended; date not announced
1.9EOL · Ended; date not announced
1.8EOL · Ended; date not announced
1.7EOL · Ended; date not announced
1.6EOL · Ended; date not announced
1.5EOL · Ended; date not announced
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 |
|---|---|---|---|---|---|---|
| 1.14 | May 27, 2020 | Maintained | Date not announced | 1.14.5 | Yes | Active |
| 1.13 | Oct 30, 2019 | Ended | Ended; date not announced | 1.13.0 | No | EOL |
| 1.12 | Apr 24, 2019 | Ended | Ended; date not announced | 1.12.2 | No | EOL |
| 1.11 | Oct 30, 2018 | Ended | Ended; date not announced | 1.11.1 | No | EOL |
| 1.10 | Apr 12, 2018 | Ended | Ended; date not announced | 1.10.8 | Yes | EOL |
| 1.9 | Aug 5, 2015 | Ended | Ended; date not announced | 1.9.12 | Yes | EOL |
| 1.8 | Jun 18, 2013 | Ended | Ended; date not announced | 1.8.19 | Yes | EOL |
| 1.7 | Oct 11, 2011 | Ended | Ended; date not announced | 1.7.22 | Yes | EOL |
| 1.6 | Mar 20, 2009 | Ended | Ended; date not announced | 1.6.23 | Yes | EOL |
| 1.5 | Jun 19, 2008 | Ended | Ended; date not announced | 1.5.9 | Yes | EOL |
| 1.4 | Sep 10, 2006 | Ended | Ended; date not announced | 1.4.6 | Yes | EOL |
| 1.3 | Dec 30, 2005 | Ended | Ended; date not announced | 1.3.2 | Yes | EOL |
| 1.2 | May 21, 2005 | Ended | Ended; date not announced | 1.2.3 | Yes | EOL |
| 1.1 | Sep 29, 2004 | Ended | Ended; date not announced | 1.1.4 | Yes | EOL |
| 1.0 | Feb 23, 2004 | Ended | Ended; date not announced | 1.0.9 | Yes | EOL |
Data sources
Embed this badge
Show Apache Subversion'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/apache-subversion/)HTML
<a href="https://eol.wiki/apache-subversion/"><img src="https://eol.wiki/badge/apache-subversion.svg" alt="Apache Subversion end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Apache Subversion have reached end of life?
The following Apache Subversion versions have reached end of life and no longer receive security updates: 1.13, 1.12, 1.11, 1.10, 1.9, 1.8, 1.7, 1.6 (and 6 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Apache Subversion 1.13?
Apache Subversion 1.13 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 Apache Subversion?
The latest version of Apache Subversion is 1.14.5, released in the 1.14 release cycle.
How many versions of Apache Subversion are currently supported?
Apache Subversion currently has 1 actively supported version(s): 1.14.
When does Apache Subversion 1.14 reach end of life?
Apache Subversion 1.14 does not have a specific end-of-life date announced yet.
What should I do when Apache Subversion reaches end of life?
When a Apache Subversion 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.