rusackas opened a new pull request, #42891: URL: https://github.com/apache/superset/pull/42891
### SUMMARY Stacked on #42803 (the SQLAlchemy 2.0 + flask-sqlalchemy 3.1.1 core bump) — **base branch is `experiment/sqla2-full-bump`, not `master`.** Rebase onto master once #42803 merges. `pyproject.toml` already had five optional DB-connector extras explicitly capped below their SQLAlchemy-2.0-only releases, each commented "bump in lockstep with Superset's own SQLAlchemy 2.0 core bump (discussion #40273), not before": | Extra | Before | After | |---|---|---| | `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` | That core bump has now landed in #42803, so this widens all five. Each dialect cuts hard from a 1.4-only line to a 2.0-only line with no dual-compat release, hence the hard floor bump rather than a widened range. All five target versions confirmed to exist on PyPI. None of the five are pinned in `requirements/base.txt`, `requirements/development.txt`, or any other lockfile — they're pure optional per-connector extras — so no lockfile regeneration was needed alongside the `pyproject.toml` change. **Does not close out discussion #40273's driver survey entirely.** Five other extras remain blocked on their own upstream SQLAlchemy 2.0 support, independent of Superset's bump (see each package's comment / `known_incompatibilities` metadata in the corresponding `db_engine_specs/*.py`): - `aurora-data-api` — both available forks have unresolved SQLAlchemy 2.0 breaks - `d1` — only release explicitly excludes SQLAlchemy 2.0 - `kusto` — upstream hard-pins `sqlalchemy==1.4.*` - `solr` — unmaintained, hard-pinned to ~1.4.7 - `ocient` — closed-source vendor package, 2.0 support unverified ### TESTING INSTRUCTIONS `pyproject.toml`-only change (no code paths touched). Verified all five target versions exist via `pip index versions`. Confirmed via `./scripts/uv-pip-compile.sh` inputs (`requirements/*.in`) that none of these five extras feed any lockfile, so no regeneration is required. ### ADDITIONAL INFORMATION - [ ] Has associated issue - [ ] Required feature flags: - [ ] Changes UI - [ ] Includes DB Migration - [ ] Introduces new feature or API - [ ] Removes existing feature or API -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
