rusackas commented on PR #45411: URL: https://github.com/apache/superset/pull/45411#issuecomment-6329558833
Dug in a bit further on this one. Past the `paginated_update`/psycopg3 stuff from before, bumping the floor to 2.1.4 also breaks `requirements/development.txt` resolution outright: `sqlalchemy-risingwave`'s latest release (2.1.0) still pins `SQLAlchemy<2.1,>=2.0`, with nothing newer on PyPI (checked including pre-releases). That's not just a dev-extras/test-coverage issue either - `risingwave://` connections are registered by that same dialect package, so `pip install apache-superset[risingwave]` would become flat-out unresolvable once core moves past 2.0.x. We'd be dropping RisingWave support entirely until upstream ships a 2.1-compatible release. Between that and the migration-helper/driver-default issues already flagged, this isn't a dependabot-sized fix. Holding it - will need an actual migration PR once sqlalchemy-risingwave catches up, or a deliberate call to drop RisingWave support in the meantime. -- 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]
