All status pages · Unowned issues across all projects · How to write a weekly status report from GitHub

Weekly status: apache/airflow

2026-10-08 to 2026-10-15 (7 days). Unofficial: generated from this repository’s public GitHub activity by pilotless status. Not affiliated with the project, and no information here that GitHub does not publish.

100+ commits by 46 people, at least 41 pull requests merged, 100 open pull requests, 16 open issues on this page of results.

Stalled pull requests

Open, and untouched for seven days or more:

#34487 Add watchdog for immediately processing changes in the DAGs folder - last touched 850 days ago
#30531 [WIP] Migrate core EmailOperator to SMTP provider - last touched 451 days ago
#36504 [POC][WIP] Async SQLAlchemy sessions in Airflow - last touched 154 days ago
#68014 Make required airflowctl body fields positional - last touched 87 days ago
#66852 Add tasks clear command to airflowctl - last touched 86 days ago

Issues nobody has picked up

Open, unassigned, and with no replies yet:

#74756 @teardown task raises ValueError when called twice, and gets the wrong trigger rule with e - opened 0 days ago
#74699 EcsRunTaskOperator fails with ResourceNotFoundException instead of its own error or skip w - opened 1 days ago

The two lists above are what a status meeting is usually for. Nobody had to attend one to produce this page.

If you maintain apache/airflow and would rather this page did not exist, open an issue and it will be deleted - no argument, no reply needed beyond the repository name.

Want this for your own repositories? Install the pilotless GitHub App — one click, then a pinned weekly status digest in each selected repo. Prefer CI-only? The status-action is still two lines of YAML with no account and nothing leaving GitHub.