You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dependabot[bot] (via GitHub)" <gi...@apache.org> on 2026/10/17 07:03:27 UTC
[PR] chore(deps): bump sqlalchemy from 2.0.52 to 2.1.4 [superset]
dependabot[bot] opened a new pull request, #45411:
URL: https://github.com/apache/superset/pull/45411
Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.52 to 2.1.4.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/sqlalchemy/sqlalchemy/releases">sqlalchemy's releases</a>.</em></p>
<blockquote>
<h1>2.1.4</h1>
<p>Released: October 7, 2026</p>
<h2>orm</h2>
<ul>
<li>
<p><strong>[orm] [bug] [regression]</strong> Fixed regression caused by <a href="https://www.sqlalchemy.org/trac/ticket/13333">#13333</a> where assigning a
<code>MetaData</code> object to the <code>metadata</code> attribute of a mapped
Declarative class, in order to place that class's <code>Table</code> in a
<code>MetaData</code> collection other than that of the
<code>_orm.registry</code>, would emit a warning that the attribute name
<code>metadata</code> should be left reserved. The warning is now emitted only
when the <code>metadata</code> attribute is assigned to an object other than a
<code>MetaData</code>.</p>
<p>References: <a href="https://www.sqlalchemy.org/trac/ticket/13659">#13659</a></p>
</li>
</ul>
<h2>engine</h2>
<ul>
<li>
<p><strong>[engine] [bug] [regression]</strong> Fixed regression from the 1.4 series where the DBAPI cursor used for a
compiled statement that returns no rows, which includes DDL constructs
such as <code>CreateTable</code> and <code>DropTable</code> as well as the
SAVEPOINT, ROLLBACK TO SAVEPOINT and RELEASE SAVEPOINT statements emitted
by <code>_engine.Connection.begin_nested()</code>, was not closed after
execution, and was instead left to be released when garbage collected.
The cursor is now closed immediately, as was the case in 1.3 and as is
already the case for INSERT, UPDATE, DELETE and <code>_sql.text()</code>
statements.</p>
<p>This change is also <strong>backported</strong> to: 2.0.55</p>
<p>References: <a href="https://www.sqlalchemy.org/trac/ticket/13640">#13640</a></p>
</li>
<li>
<p><strong>[engine] [bug]</strong> Fixed issue in the
<code>_engine.Connection.execution_options.logging_token</code> option
where setting the value to <code>None</code> or another false value would raise
<code>AttributeError</code> if a logging token had not already been established on
that <code>_engine.Connection</code>, such as on a newly checked out
connection, when the option was set at the <code>_engine.Engine</code> level,
or when the token was reset to <code>None</code> more than once. Regression
introduced in 2.0.30 as part of <a href="https://www.sqlalchemy.org/trac/ticket/11210">#11210</a>.</p>
<p>This change is also <strong>backported</strong> to: 2.0.55</p>
<p>References: <a href="https://www.sqlalchemy.org/trac/ticket/13641">#13641</a></p>
</li>
<li>
<p><strong>[engine] [bug] [regression]</strong> Fixed regression where iterating a <code>Result</code> directly would create
reference cycles that prevented the <code>Result</code> along with the DBAPI</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a href="https://github.com/sqlalchemy/sqlalchemy/commits">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] chore(deps): bump sqlalchemy from 2.0.52 to 2.1.5 [superset]
Posted by "dependabot[bot] (via GitHub)" <gi...@apache.org>.
dependabot[bot] commented on PR #45411:
URL: https://github.com/apache/superset/pull/45411#issuecomment-6396375901
Looks like sqlalchemy is no longer being updated by Dependabot, so this is no longer needed.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] chore(deps): bump sqlalchemy from 2.0.52 to 2.1.4 [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on PR #45411:
URL: https://github.com/apache/superset/pull/45411#issuecomment-6306541072
Checked this one out and ran the unit suite on 2.1.5 locally... not a drop-in bump. `superset-core` still pins `sqlalchemy<2.1` (which is why nothing even installs here), and past that, 2.1 flips `postgresql://` to psycopg3 by default and stops accepting an ORM `Query` in `session.execute`, which `paginated_update` in the migration helpers relies on. That wants an actual migration PR rather than a dependabot bump.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] chore(deps): bump sqlalchemy from 2.0.52 to 2.1.4 [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] chore(deps): bump sqlalchemy from 2.0.52 to 2.1.5 [superset]
Posted by "dependabot[bot] (via GitHub)" <gi...@apache.org>.
dependabot[bot] closed pull request #45411: chore(deps): bump sqlalchemy from 2.0.52 to 2.1.5
URL: https://github.com/apache/superset/pull/45411
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org