This is an automated email from the ASF dual-hosted git repository. jedcunningham pushed a commit to branch v2-2-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 4ff0ab16868d7e7b765a4ab1d285088cd1f162fe Author: Jarek Potiuk <ja...@potiuk.com> AuthorDate: Mon Jan 31 19:23:58 2022 +0100 Limit SQLAlchemy to < 1.4.0 for 2.2.* line (#21235) The recent release of FAB 3.4.4 has unblocked us from upgrading SQLAlchemy to 1.4.* version. We wanted to do it for quite some time however upgrading to 1.4.* of sqlalchemy and allowing our users to use it for 2.2.4 is a bit risky. We are fixing resulting "aftermath" in the main branch and as of this commit there are two fixes merged and remaining MsSQL problem. The MSSql problem does not affect 2.2.4 as MsSQL will be available only starting from 2.3.0, however the two other problems have shown that SQLAlchemy has a potential to break things and we might want to test it more thoroughly before releasing 2.3.0. The problems in question are #21205 and #21228. Both were only test problems but the indicate that there might be more hidden issues involved. In order to limit risks, this PR proposes to limit SQLAlchemy for 2.2.* to < 1.4.0. This will allow to upgrade FAB and related dependencies without opening up Airflow to upgrade to SQLAlchemy 1.4 (yet). --- setup.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/setup.cfg b/setup.cfg index c3cce1c..7ab5c77 100644 --- a/setup.cfg +++ b/setup.cfg @@ -145,7 +145,7 @@ install_requires = python3-openid~=3.2 rich>=9.2.0 setproctitle>=1.1.8, <2 - sqlalchemy>=1.3.18 + sqlalchemy>=1.3.18, <1.4.0 sqlalchemy_jsonfield~=1.0 tabulate>=0.7.5, <0.9 tenacity>=6.2.0