Thanks for spearheading this, Vincent. Exciting to see it finally happening.
If you / anyone gets hold of a good prompt for AI, do share it on the Github issues so that others can benefit from it as well. Thanks & Regards, Amogh Desai On Thu, Oct 16, 2025 at 10:59 PM Beck, Vincent <[email protected]> wrote: > Hi everyone, > > We are getting close to be able to migrate to SQL2. Currently we are still > limiting sqlalchemy to version 1 ( > https://github.com/apache/airflow/blob/main/providers/fab/pyproject.toml#L80) > because our type annotations across the codebase is not compatible with > SQLA2. When SQLA2 is enabled, mypy gets very angry and report a lot of > static errors as you can see in > https://github.com/apache/airflow/pull/56212. > > The idea is, to migrate to SQLA2 but also to improve type safety and code > quality, solve all these static errors. There are currently: > > * 525 errors in core Airflow > * 193 errors in providers > * 4 errors in task SDK > * 2 errors in devel-common > > Given the number of errors, I need you 😊 By dividing and conquering, we > can easily and quickly solve these errors. To make it easy I created 2 > issues, one tracking errors in core Airflow, one tracking errors in > providers. No need to create issue for Task SDK and devel-common, there are > just a few. > > > * Issue tracking errors in core Airflow: > https://github.com/apache/airflow/issues/56735 > * Issue tracking errors in providers: > https://github.com/apache/airflow/issues/56738 > > In these issues you can find steps on how to generate these errors. If you > are interested to help Airflow using SQLA2, then please feel free to > pick-up some files/directories as part of these issues and resolve the > errors in these files. Solving these static errors is not complicated, > there are just a lot 😊 > > Thank you for your help! > Vincent >
