-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement] Re-add support for SQLAlchemy 1.4 #55435
Conversation
Please sign off the commit. Thanks |
Signed-off-by: Maciek Bryński <[email protected]>
Head branch was pushed to by a user without write access
39bd4a9
to
86f84b1
Compare
[Java-Extensions Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
[FE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
Done |
[BE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
@Mergifyio backport branch-3.4 |
✅ Backports have been created
|
Changing SQLAlchemy version from >=2.0 to >=1.4 Signed-off-by: Maciek Bryński <[email protected]> (cherry picked from commit 7f7ac0d)
@Astralidea |
in BI_integrations Apache Superset case, also need SQLAlchemy 1.4 |
I will release version 1.2.1 today. |
Why I'm doing:
Changing SQLAlchemy version from
>=2.0
to>=1.4
What I'm doing:
Fixes #55434
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check: