Apache Airflow EOL: end-of-life dates for every Airflow version
Apache Airflow 2 reached end of life on 22 April 2026, and 2.11.2, released on 14 March 2026, was its last release. The Airflow project lists Airflow 3 as one line in Maintenance, currently 3.4.0 from 6 November 2026, with no end date announced. OSSeva patches Airflow 2.x after end of life. Dates checked against airflow.apache.org and endoflife.date on 19 November 2026.
- Latest release
- 3.4.0
- Supported lines
- 1
- End-of-life lines
- 9
- Next end of life
- None scheduled
Airflow 2 has ended
Migrate to Airflow 3, or keep Airflow 2 patched
Airflow 3 removes SubDAGs, SLAs and direct metadata database access from tasks, so many estates need weeks of DAG work first. OSSeva patches Airflow 2.x after end of life while that work is scoped. Other versions are assessed case by case through a version coverage check. Critical fixes ship within 48 hours and High within 7 days.
Who patches Apache Airflow after end of life
OSSeva provides Apache Airflow extended support: patched, signed builds for Apache Airflow 2 after upstream support ends, plus 24/7 operations on the Operate tier.
Apache Airflow release timeline
All Apache Airflow versions, release dates and end-of-life dates
| Version | Released | Active Support | Limited Support | Latest | OSSeva |
|---|---|---|---|---|---|
| 3.4 | 15 days ago(7 Nov 2026) | Yes | Yes | 3.4.0 | – |
| 3.3 | 5 months ago(6 Jul 2026) | Ended 15 days ago(7 Nov 2026) | Ended 15 days ago(7 Nov 2026) | 3.3.2 | – |
| 3.2 | 8 months ago(7 Apr 2026) | Ended 5 months ago(6 Jul 2026) | Ended 5 months ago(6 Jul 2026) | 3.2.2 | – |
| 3.1 | 1 year and 2 months ago(25 Sept 2025) | Ended 8 months ago(7 Apr 2026) | Ended 8 months ago(7 Apr 2026) | 3.1.8 | – |
| 3.0 | 1 year and 7 months ago(22 Apr 2025) | Ended 1 year and 2 months ago(25 Sept 2025) | Ended 1 year and 2 months ago(25 Sept 2025) | 3.0.6 | – |
| 2 | 5 years and 11 months ago(17 Dec 2020) | Ended 1 year and 1 month ago(22 Oct 2025) | Ended 7 months ago(22 Apr 2026) | 2.11.2 | Patched |
| 1.10 | 8 years and 3 months ago(27 Aug 2018) | Ended 5 years and 11 months ago(17 Dec 2020) | Ended 5 years and 5 months ago(17 Jun 2021) | 1.10.15 | – |
| 1.9 | 8 years and 11 months ago(2 Jan 2018) | Ended 8 years and 3 months ago(27 Aug 2018) | Ended 8 years and 3 months ago(27 Aug 2018) | 1.9.0 | – |
| 1.8 | 9 years and 6 months ago(9 May 2017) | Ended 8 years and 11 months ago(3 Jan 2018) | Ended 8 years and 11 months ago(3 Jan 2018) | 1.8.2 | – |
| 1.7 | 10 years and 8 months ago(28 Mar 2016) | Ended 9 years and 8 months ago(19 Mar 2017) | Ended 9 years and 8 months ago(19 Mar 2017) | 1.7.1.2 | – |
Lifecycle data from endoflife.date (MIT licence), refreshed 21 Nov 2026. Upstream policy: github.com. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.
Airflow 2 and Airflow 3 support status
The Airflow project does not publish a support window for each Airflow 3 minor. Its supported-versions page lists "3" as a single line in Maintenance with the limited-maintenance and end dates marked TBD, and says EOL versions get no fixes or support. endoflife.date tracks each 3.x minor and ends it when the next minor ships, which is why it shows 3.0 to 3.3 as ended. Treat those per-minor dates as endoflife.date's reading, not an Airflow announcement, and plan to stay on the latest 3.x.
Airflow support status. Sources: airflow.apache.org supported-versions page and endoflife.date, read on 19 November 2026.
| Line | First release | Upstream status | Latest release |
|---|---|---|---|
| Airflow 2 | 17 Dec 2020 | Limited maintenance from 22 Oct 2025; end of life 22 Apr 2026 | 2.11.2, 14 Mar 2026 |
| Airflow 3 (line) | 22 Apr 2025 | Maintenance, end date TBD | 3.4.0, 6 Nov 2026 |
| 3.3 | 6 Jul 2026 | Ended 7 Nov 2026 (endoflife.date) | 3.3.2, 17 Sep 2026 |
| 3.2 | 7 Apr 2026 | Ended 6 Jul 2026 (endoflife.date) | 3.2.2, 29 May 2026 |
| 3.1 | 25 Sep 2025 | Ended 7 Apr 2026 (endoflife.date) | 3.1.8, 11 Mar 2026 |
| 3.0 | 22 Apr 2025 | Ended 25 Sep 2025 (endoflife.date) | 3.0.6, 29 Aug 2025 |
Migrating Airflow 2 to 3: what breaks
Airflow's upgrade guide starts from Airflow 2.7 or later, and recommends reaching the latest 2.x first. Because 2.11.2 is the last 2.x release and is itself end of life, that first step now runs on an unpatched version. The guide separates what DAG authors change from what the deployment team changes.
The change most likely to cost time is database access. In Airflow 3, tasks can no longer query the metadata database directly and must go through the Task Execution API or the Airflow Python Client. Any custom operator or hook that imports a session or runs SQL against Airflow's own tables has to be rewritten. The guide calls the DbApiHook workaround discouraged because it will break in future releases.
Airflow 2 to 3 changes that break DAGs or deployments. Source: Airflow upgrading-to-Airflow-3 guide, read on 19 November 2026.
| Area | Change in Airflow 3 | What to do |
|---|---|---|
| Task database access | Tasks cannot query the metadata database directly | Move to the Airflow Python Client or Task Execution API |
| SubDAGs | Removed | Rebuild with TaskGroups, Assets or data-aware scheduling |
| SLAs | Removed | Replace with Deadline Alerts |
| Executors | Sequential Executor, CeleryKubernetesExecutor and LocalKubernetesExecutor removed | Use LocalExecutor, or the multiple-executor configuration |
| Context variables | execution_date, next_ds, prev_ds, tomorrow_ds, yesterday_ds and related variables removed | Use logical_date and the data interval instead |
| Imports | DAG, task decorators, BaseOperator, Connection and Variable move to airflow.sdk; Dataset becomes Asset | Run Ruff with the AIR301 and AIR302 rules (Ruff 0.13.1 or later) |
| Scheduling defaults | catchup_by_default is False; bare cron strings use CronTriggerTimetable | Set create_cron_data_intervals = True before upgrading to keep old intervals |
| REST API | /api/v1 replaced by /api/v2 | Update every external caller |
| Web and auth | Simple Auth manager is the default; auth routes get an /auth prefix; startup uses airflow api-server and airflow dag-processor | Install the FAB provider to keep FabAuthManager; update OAuth callback URLs |
Back up the metadata database and run airflow db clean before airflow db migrate, as the guide advises. xcom_pull() without task_ids now reads only from the current task, which silently changes results rather than raising an error.
Airflow in the rest of a data platform
Airflow usually sits inside a wider data platform. Apache NiFi and Apache Flink have their own lifecycle pages: [NiFi end of life](/eol/nifi) and [Flink end of life](/eol/flink). Airflow DAGs run on Python, so the interpreter's own dates matter too: see [Python end of life](/eol/python).
Running an end-of-life Apache Airflow version?
OSSeva keeps end-of-life Apache Airflow patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.
Apache Airflow extended supportIs Apache Airflow 2 end of life?
Yes. The Airflow supported-versions page gives Airflow 2 an end of life date of 22 April 2026, after limited maintenance from 22 October 2025. The last release was 2.11.2 on 14 March 2026.
What is the latest Apache Airflow version?
Airflow 3.4.0, released on 6 November 2026, per the Airflow project and endoflife.date.
When does Airflow 3 reach end of life?
The Airflow project lists Airflow 3 as one line in Maintenance with no end date announced. endoflife.date ends each 3.x minor when the next one is released, so it shows 3.3 as ended on 7 November 2026. Stay on the latest 3.x minor.
Can I upgrade straight from Airflow 2.x to 3?
The upgrade guide starts from Airflow 2.7 or later and recommends the latest 2.x first. It also asks you to run Ruff's AIR rules, back up the metadata database and run airflow db migrate.
What breaks when moving from Airflow 2 to Airflow 3?
Direct metadata database access from tasks, SubDAGs, SLAs, the Sequential Executor, the /api/v1 REST API and many context variables such as execution_date, per the upgrade guide. Import paths also move to airflow.sdk.
Who provides Airflow support after end of life?
OSSeva patches Airflow 2.x after end of life and assesses other versions case by case through a version coverage check. This page does not compare other providers.
Which Apache Airflow versions are still supported?
3.4. Every other line has reached end of life, per the dates in the table above.
Can I get security patches for an end-of-life Apache Airflow version?
Yes. OSSeva ships signed builds with backported CVE fixes for Apache Airflow 2 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.
Who provides Apache Airflow support after end of life?
OSSeva provides Apache Airflow extended support: patched, signed builds for Apache Airflow 2 after upstream support ends, plus 24/7 operations on the Operate tier.
Get a quote
Still running an end-of-life Apache Airflow?
Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.
Prefer to talk or read more first?