Note

This page shows plans and intentions for upcoming releases of various Airflow components / packages. It is NOT a commitment that releases will happen with planned content at planned times. It is rather a outlook and tool to collaborate.

Completed releases will be documented via https://airflow.apache.org/docs/ and the corresponding release notes of the individual packages

The release calendar is availabe as public Google Calendar. The iCal version is also available

Support for Airflow in Providers

Currently, Providers are supporting Airflow 2.11+.

The following changes are planned to support Airflow in newly released providers:

  • In May 2026, we will move to >= Airflow 3.1 as Airflow 2.11.0 was released in May 2025 and Airflow 3.0 was released in April 2025

Airflow Core

See Airflow 3.x#Airflow3adoptionfocus

Provider Releases

Release manager rotational team: Jens Scheffler Jarek Potiuk  Vincent BECK Shahar Epstein 

Planned Cut Date: Every second TuesdayRelease ManagerScope / Notes

 

Jarek Potiuk 

Released + rc2 ad-hoc

 

Shahar Epstein

 

Vincent BECK 


 

Jens Scheffler 


 

Jarek Potiuk 


Airflow Ctl

Release manager rotational team: Buğra Öztürk Jarek Potiuk 

Release/Cut DateRelease managerVersionScope / Notes

Week of

Buğra Öztürk 

0.1.3

Released

Week of  

Jarek Potiuk 

0.1.4

 In-progress

Airflow Helm Chart

Release manager rotational team: Jedidiah Cunningham Jens Scheffler Buğra Öztürk Jarek Potiuk 

Planned Cut Date: Every 3rd Week in a month (Date displayed for Mondays each)Release ManagerScope / Notes

Week of 

Buğra Öztürk 

1.21.0?

Scope?

Week of  

Jarek Potiuk 


Week of  

Jedidiah Cunningham 


Airflow 2

Release manager: Jarek Potiuk 

Planned Cut DateRelease ManagerScope / Notes

Week of  

Jarek Potiuk 

Released

Week of

Jarek Potiuk 

This will be the last release of Airflow 2.



  • No labels

4 Comments

  1. Buğra Öztürk

    If this is a generic document for Airflow and its distributions. Should we include the airflowctl  here? I see, of course, this is still in draft slightly smiling face . Just making suggestions

    1. Jarek Potiuk

      Yes. And Yes. And Feel free :) 

    2. Jens Scheffler

      Yeah is a DRAFT proposal to keep a page with planned releases, not agreed upon that we use this but at least for providers make sense.

      Also in my view all other packages can go in, and if somebody has a better idea for a structure I am open. (First we thought about a Google calendar but then this must be owned by one person and Confluence does not have a better calendar widget unfortunately)

      1. Buğra Öztürk

        It looks good. I was trying to understand what we are planning with this page :)

        I tried something similar in this one. I updated until 0.1.0 decision but would be happy to move here and follow similar approach within the same place. I will add airflowctl and update accordingly. Maybe we should go organically on this one. There are of course similar parameters such as supported airflow-core or airflow-core API version in the airflowctl case but it would be easier to see by the time which information we need to keep

        https://cwiki.apache.org/confluence/x/TxBJFg