← ← Back to all products
Apache Airflow
Active
Middleware Latest Version: 3.2.2 Latest Release: May 29, 2026
Apache Airflow is a platform for programmatically authoring, scheduling, and monitoring data workflows.
Versions
6
Latest Version
3.2.2
Active Support
1
EOL
5
Lifecycle Timeline
Today ↓
3
3
2
2
1.10
1.10
1.9
1.9
1.8
1.8
1.7
1.7
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 3 | Apr 22, 2025 | Yes | No | 3.2.2 | No | Active |
| 2 | Dec 17, 2020 | Oct 22, 2025 | Apr 22, 2026 | 2.11.2 | No | EOL |
| 1.10 | Aug 27, 2018 | Dec 17, 2020 | Jun 17, 2021 | 1.10.15 | No | EOL |
| 1.9 | Jan 2, 2018 | Aug 27, 2018 | Aug 27, 2018 | 1.9.0 | No | EOL |
| 1.8 | May 9, 2017 | Jan 3, 2018 | Jan 3, 2018 | 1.8.2 | No | EOL |
| 1.7 | Mar 28, 2016 | Mar 19, 2017 | Mar 19, 2017 | 1.7.1.2 | No | EOL |
Frequently Asked Questions
Which versions of Apache Airflow have reached end of life?
The following Apache Airflow versions have reached end of life and no longer receive security updates: 2, 1.10, 1.9, 1.8, 1.7. It is recommended to upgrade to a supported version.
Is it safe to continue using Apache Airflow 2?
Apache Airflow 2 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 Airflow?
The latest version of Apache Airflow is 3.2.2, released in the 3 release cycle.
How many versions of Apache Airflow are currently supported?
Apache Airflow currently has 1 actively supported version(s): 3.
When does Apache Airflow 3 reach end of life?
Apache Airflow 3 does not have a specific end-of-life date announced yet.
What should I do when Apache Airflow reaches end of life?
When a Apache Airflow 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.