You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@superset.apache.org by ru...@apache.org on 2026/08/07 16:33:23 UTC

(superset) branch chore/bump-sqla2-compatible-driver-caps created (now 97b7021aa5c)

This is an automated email from the ASF dual-hosted git repository.

rusackas pushed a change to branch chore/bump-sqla2-compatible-driver-caps
in repository https://gitbox.apache.org/repos/asf/superset.git


      at 97b7021aa5c chore(deps): widen 5 driver caps that were held back for the SQLAlchemy 2.0 core bump

This branch includes the following new commits:

     new 97b7021aa5c chore(deps): widen 5 driver caps that were held back for the SQLAlchemy 2.0 core bump

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



(superset) 01/01: chore(deps): widen 5 driver caps that were held back for the SQLAlchemy 2.0 core bump

Posted by ru...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

rusackas pushed a commit to branch chore/bump-sqla2-compatible-driver-caps
in repository https://gitbox.apache.org/repos/asf/superset.git

commit 97b7021aa5c8c010cac323d1404bb7d95a6fca10
Author: Claude Code <no...@anthropic.com>
AuthorDate: Fri Aug 7 09:33:02 2026 -0700

    chore(deps): widen 5 driver caps that were held back for the SQLAlchemy 2.0 core bump
    
    dremio, exasol, firebird, redshift, and risingwave each cut hard from a
    SQLAlchemy-1.4-only line to a SQLAlchemy-2.0-only line with no
    dual-compat release in between. pyproject.toml already documented each
    cap as "bump in lockstep with Superset's own SQLAlchemy 2.0 core bump
    (discussion #40273), not before" -- that bump has now landed (#42803),
    so this widens all five to their 2.0-compatible ranges:
    
    - dremio: sqlalchemy-dremio>=1.2.1,<3.0.5 -> >=3.0.5,<4
    - exasol: sqlalchemy-exasol>=2.4.0,<6.0.0 -> >=6.0.0,<8.0
    - firebird: sqlalchemy-firebird>=0.8.0,<2.0.0 -> >=2.2.0
    - redshift: sqlalchemy-redshift>=0.8.1,<0.9 -> >=1.0.0
    - risingwave: sqlalchemy-risingwave>=1.4.1,<2.0.0 -> >=2.0.0
    
    None of these five are pinned in requirements/base.txt,
    requirements/development.txt, or any other lockfile -- they're purely
    optional per-connector extras -- so no lockfile regeneration is
    needed alongside this pyproject.toml change.
    
    This does not close out discussion #40273's driver survey entirely:
    aurora-data-api, d1, kusto, solr, and ocient remain blocked on their
    own upstream SQLAlchemy 2.0 support (or, for ocient, unverified
    compatibility), independent of Superset's own bump.
---
 pyproject.toml | 37 +++++++++++++++++--------------------
 1 file changed, 17 insertions(+), 20 deletions(-)

diff --git a/pyproject.toml b/pyproject.toml
index e1be41bd211..a25e08e1f71 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -164,11 +164,10 @@ databricks = [
 datafusion = ["flightsql-dbapi>=0.2.2, <0.3"]
 db2 = ["ibm-db-sa<=0.4.4, >=0.4.4"]
 denodo = ["denodo-sqlalchemy>=2.0.5,<2.1.0"]
-# sqlalchemy-dremio 3.0.5+ hard-pins sqlalchemy~=2.0.41, dropping 1.4; 3.0.4
-# is the last dual-compat release. Capped below 3.0.5 for now; widen back to
-# <4 in lockstep with Superset's own SQLAlchemy 2.0 core bump (discussion
-# #40273), not before.
-dremio = ["sqlalchemy-dremio>=1.2.1, <3.0.5"]
+# sqlalchemy-dremio 3.0.5+ hard-pins sqlalchemy~=2.0.41, dropping 1.4.
+# Widened now that Superset's own SQLAlchemy 2.0 core bump has landed
+# (discussion #40273).
+dremio = ["sqlalchemy-dremio>=3.0.5, <4"]
 # <2 was an artificial ceiling; upstream has no SQLAlchemy version cap and
 # 1.1.10 already supports SQLAlchemy 2.0 (added `import_dbapi` in 1.1.7).
 drill = ["sqlalchemy-drill>=1.1.10, <3"]
@@ -181,10 +180,9 @@ dynamodb = ["pydynamodb>=0.8.2"]
 solr = ["sqlalchemy-solr>=0.2.4.3"]
 elasticsearch = ["elasticsearch-dbapi>=0.2.13, <0.3.0"]
 # sqlalchemy-exasol cuts hard from SQLAlchemy 1.4-only (<6.0.0) to 2.0-only
-# (>=6.0.0) with no dual-compat release. Capped below 6.0.0 for now; bump to
-# >=6.0.0,<8.0 in lockstep with Superset's own SQLAlchemy 2.0 core bump
-# (discussion #40273), not before.
-exasol = ["sqlalchemy-exasol>=2.4.0, <6.0.0"]
+# (>=6.0.0) with no dual-compat release. Bumped now that Superset's own
+# SQLAlchemy 2.0 core bump has landed (discussion #40273).
+exasol = ["sqlalchemy-exasol>=6.0.0, <8.0"]
 excel = ["xlrd>=2.0.2, <2.1"]
 # Async dashboard "Export Data/Images to Excel": uploads the workbook to S3 and
 # emails a pre-signed link. boto3 is imported lazily by superset.utils.s3, so
@@ -199,9 +197,9 @@ fastmcp = [
 ]
 # sqlalchemy-firebird >=2.0.0 unconditionally requires SQLAlchemy 2.0 on
 # Python >=3.8 (which covers Superset's >=3.11 floor), with no dual-compat
-# release. Capped below 2.0.0 for now; bump to >=2.2.0 in lockstep with
-# Superset's own SQLAlchemy 2.0 core bump (discussion #40273), not before.
-firebird = ["sqlalchemy-firebird>=0.8.0, <2.0.0"]
+# release. Bumped now that Superset's own SQLAlchemy 2.0 core bump has
+# landed (discussion #40273).
+firebird = ["sqlalchemy-firebird>=2.2.0"]
 firebolt = ["firebolt-sqlalchemy>=1.1.2, <2"]
 gevent = ["gevent>=26.7.0"]
 gsheets = ["shillelagh[gsheetsapi]>=1.4.4, <2"]
@@ -240,15 +238,14 @@ presto = ["pyhive[presto]>=0.6.5"]
 trino = ["trino>=0.338.0"]
 prophet = ["prophet>=1.3.0, <2"]
 # sqlalchemy-redshift cuts hard from SQLAlchemy 1.4-only (0.8.x) to 2.0-only
-# (>=1.0.0) with no dual-compat release; the existing <0.9 ceiling already
-# keeps this on the 1.4-only line. Bump to >=1.0.0 in lockstep with
-# Superset's own SQLAlchemy 2.0 core bump (discussion #40273), not before.
-redshift = ["sqlalchemy-redshift>=0.8.1, <0.9"]
+# (>=1.0.0) with no dual-compat release. Bumped now that Superset's own
+# SQLAlchemy 2.0 core bump has landed (discussion #40273).
+redshift = ["sqlalchemy-redshift>=1.0.0"]
 # No release of sqlalchemy-risingwave has ever supported both SQLAlchemy 1.4
-# and 2.0 (version numbers don't track SQLAlchemy compat monotonically); pin
-# to the newest 1.4-only release for now. Bump to >=2.0.0 in lockstep with
-# Superset's own SQLAlchemy 2.0 core bump (discussion #40273), not before.
-risingwave = ["sqlalchemy-risingwave>=1.4.1, <2.0.0"]
+# and 2.0 (version numbers don't track SQLAlchemy compat monotonically).
+# Bumped to the 2.0-only line now that Superset's own SQLAlchemy 2.0 core
+# bump has landed (discussion #40273).
+risingwave = ["sqlalchemy-risingwave>=2.0.0"]
 shillelagh = ["shillelagh[all]>=1.4.4, <2"]
 singlestore = ["sqlalchemy-singlestoredb>=1.2.1, <2"]
 snowflake = ["snowflake-sqlalchemy>=1.11.0, <2"]