+1 on this - just one comment, we need to add it to https://cwiki.apache.org/confluence/display/AIRFLOW/Release+Plan and have - ideally - rotational release managers :) - not that we expect **many** changes there, but it would be great to have volunteer release managers to committed to release it.
We have a number of releases happening now .. and it's getting more complicated, so it would be great if we have clarity about who will release it when it changes. J On Sun, Apr 12, 2026 at 9:42 PM Hussein Awala <[email protected]> wrote: > Hello everyone, > > Following the discussion thread > https://lists.apache.org/thread/l7f3nyww68z6hc92ftxzbgf397wjnz0x from > March > 23, I'd like to call for a lazy consensus on releasing the existing MyPy > plugins as a standalone package: apache-airflow-mypy. > > *Summary* > > Apache Airflow ships two MyPy plugins (decorators and outputs) that improve > type checking for DAG authors. Currently, these plugins are not published > to PyPI, so users who want to benefit from them need to manually copy the > plugin files into their projects. > > The proposal is to publish apache-airflow-mypy as an independently > versioned package on PyPI. The package is small and self-contained (~150 > lines of code), with no runtime dependency on airflow-core or task-sdk — > only mypy itself. > > *PR*: https://github.com/apache/airflow/pull/61422 > > The package name apache-airflow-mypy has already been reserved on PyPI. > > During the discussion, the feedback was unanimously positive and no > objections were raised. > > I would like to call for a lazy consensus vote which will run for 72 hours. > If no one votes -1 during the voting period, the vote will be considered > passed and the PR will be merged. > > Thank you! > > Regards, > > Hussein >
