Hi All, I’m excited to announce that the *Sequential Executor* and *Debug Executor* have been removed from the in-tree executors in our repository, thanks to the efforts of the community! (Discussed in https://lists.apache.org/thread/65jw3o3mn7qlc56f9bt2146fmoy0z5t6).
These executors were primarily used for local testing and debugging but we have the LocalExecutor( https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/executor/local.html) which can achieve better results since it supports parallelism too. The LocalExecutor has also been ported over to use the new Airflow 3 way of running tasks using task SDK and task execution interface + API server. One of the reasons the Sequential Executor was kept around for so long was due to some "single" process restrictions while using Sqlite. With the newer versions of Sqlite supporting WAL mode, LocalExecutor now works well with Sqlite, making the SequentialExecutor redundant. [3] helped in accomplishing that. This was a long shot for Airflow 3 but we have managed to do this even before the release candidate, thanks to everyone who helped in reviewing the code and helping me get this one through. *What does this mean for you?* If you were using these executors, you should switch to alternatives. *LocalExecutor* is the easiest and the most natural replacement to any of those, but *CeleryExecutor* is a good option too if you do not mind an extra worker being spun up. I do not anticipate any major issues from this change, but do shout out on Slack, on #airflow-3-dev channel for help if you encounter something. Thanks & Best Regards, Amogh [1] - https://github.com/apache/airflow/issues/48522 [2] - https://github.com/apache/airflow/issues/48523 [3] - https://github.com/apache/airflow/pull/44839
