← ← Back to all products
Apache InLong
Active
Middleware Latest Version: 2.3.0 Latest Release: Nov 13, 2025
Apache InLong is a one-stop, full-scenario integration framework for massive data, supporting data ingestion, synchronization, and subscription with high throughput.
Versions
7
Latest Version
2.3.0
Active Support
2
EOL
5
Lifecycle Timeline
Today ↓
2.3
2.3
2.2
2.2
2.1
2.1
2.0
2.0
1.13
1.13
1.12
1.12
1.10
1.10
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2.3 | Nov 13, 2025 | Yes | No | 2.3.0 | No | Active |
| 2.2 | May 14, 2025 | Yes | No | 2.2.0 | No | Active |
| 2.1 | Jan 3, 2025 | No | Yes | 2.1.0 | No | EOL |
| 2.0 | Oct 20, 2024 | No | Yes | 2.0.0 | No | EOL |
| 1.13 | Jul 18, 2024 | No | Yes | 1.13.0 | No | EOL |
| 1.12 | Apr 21, 2024 | No | Yes | 1.12.0 | No | EOL |
| 1.10 | Dec 13, 2023 | No | Yes | 1.10.0 | No | EOL |
Frequently Asked Questions
Which versions of Apache InLong have reached end of life?
The following Apache InLong versions have reached end of life and no longer receive security updates: 2.1, 2.0, 1.13, 1.12, 1.10. It is recommended to upgrade to a supported version.
Is it safe to continue using Apache InLong 2.1?
Apache InLong 2.1 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 InLong?
The latest version of Apache InLong is 2.3.0, released in the 2.3 release cycle.
How many versions of Apache InLong are currently supported?
Apache InLong currently has 2 actively supported version(s): 2.3, 2.2.
When does Apache InLong 2.3 reach end of life?
Apache InLong 2.3 does not have a specific end-of-life date announced yet.
What should I do when Apache InLong reaches end of life?
When a Apache InLong 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.