← ← Back to all products
All badges & lifecycle API →
Apache HopEnd of Life (EOL) Dates & Support Status
Active
MiddlewareLatest Version: 2.19.0Latest Release: Aug 17, 2026
Apache Hop is a data orchestration and engineering platform for visual pipeline design.
Support summary
Apache Hop 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
0 lts
Versions
23
Latest Version
2.19.0
Active Support
1
EOL
22
Lifecycle Timeline
Oct 7, 2024As of Sep 27, 2026
2.19Active · Date not announced
2.18EOL · Aug 17, 2026
2.17EOL · Jun 1, 2026
2.16EOL · Feb 6, 2026
2.15EOL · Nov 17, 2025
2.14EOL · Aug 20, 2025
2.13EOL · May 19, 2025
2.12EOL · Apr 22, 2025
2.11EOL · Feb 19, 2025
2.10EOL · Dec 4, 2024
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 |
|---|---|---|---|---|---|---|
| 2.19 | Aug 17, 2026 | Maintained | Date not announced | 2.19.0 | No | Active |
| 2.18 | Jun 1, 2026 | Ended | Aug 17, 2026 | 2.18.1 | No | EOL |
| 2.17 | Feb 6, 2026 | Ended | Jun 1, 2026 | 2.17.0 | No | EOL |
| 2.16 | Nov 17, 2025 | Ended | Feb 6, 2026 | 2.16.0 | No | EOL |
| 2.15 | Aug 12, 2025 | Ended | Nov 17, 2025 | 2.15.0 | No | EOL |
| 2.14 | May 13, 2025 | Ended | Aug 20, 2025 | 2.14.0 | No | EOL |
| 2.13 | Apr 15, 2025 | Ended | May 19, 2025 | 2.13.0 | No | EOL |
| 2.12 | Feb 13, 2025 | Ended | Apr 22, 2025 | 2.12.0 | No | EOL |
| 2.11 | Dec 4, 2024 | Ended | Feb 19, 2025 | 2.11.0 | No | EOL |
| 2.10 | Oct 7, 2024 | Ended | Dec 4, 2024 | 2.10.0 | No | EOL |
| 2.9 | May 20, 2024 | Ended | Oct 8, 2024 | 2.9.0 | No | EOL |
| 2.8 | Feb 28, 2024 | Ended | May 20, 2024 | 2.8.0 | No | EOL |
| 2.7 | Nov 17, 2023 | Ended | Mar 13, 2024 | 2.7.0 | No | EOL |
| 2.6 | Sep 12, 2023 | Ended | Dec 1, 2023 | 2.6.0 | No | EOL |
| 2.5 | Jun 8, 2023 | Ended | Sep 12, 2023 | 2.5.0 | No | EOL |
| 2.4 | Mar 27, 2023 | Ended | Jun 8, 2023 | 2.4.0 | No | EOL |
| 2.3 | Jan 27, 2023 | Ended | Mar 27, 2023 | 2.3.0 | No | EOL |
| 2.2 | Dec 2, 2022 | Ended | Jan 27, 2023 | 2.2.0 | No | EOL |
| 2.1 | Oct 14, 2022 | Ended | Dec 7, 2022 | 2.1.0 | No | EOL |
| 2.0 | Jun 2, 2022 | Ended | Oct 14, 2022 | 2.0.0 | No | EOL |
| 1.2 | Mar 8, 2022 | Ended | Jun 2, 2022 | 1.2.0 | No | EOL |
| 1.1 | Jan 24, 2022 | Ended | Mar 8, 2022 | 1.1.0 | No | EOL |
| 1.0 | Oct 5, 2021 | Ended | Jan 24, 2022 | 1.0.0 | No | EOL |
Data sources
Sources
Embed this badge
Show Apache Hop'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-hop/)HTML
<a href="https://eol.wiki/apache-hop/"><img src="https://eol.wiki/badge/apache-hop.svg" alt="Apache Hop end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Apache Hop have reached end of life?
The following Apache Hop versions have reached end of life and no longer receive security updates: 2.18, 2.17, 2.16, 2.15, 2.14, 2.13, 2.12, 2.11 (and 14 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Apache Hop 2.18?
Apache Hop 2.18 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 Hop?
The latest version of Apache Hop is 2.19.0, released in the 2.19 release cycle.
How many versions of Apache Hop are currently supported?
Apache Hop currently has 1 actively supported version(s): 2.19.
When does Apache Hop 2.19 reach end of life?
Apache Hop 2.19 does not have a specific end-of-life date announced yet.
What should I do when Apache Hop reaches end of life?
When a Apache Hop 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.