dependabot[bot] opened a new pull request, #45687:
URL: https://github.com/apache/superset/pull/45687

   Bumps 
[sqlalchemy-continuum](https://github.com/sqlalchemy-continuum/sqlalchemy-continuum)
 from 1.8.0 to 2.0.0.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/releases";>sqlalchemy-continuum's
 releases</a>.</em></p>
   <blockquote>
   <h2>2.0.0</h2>
   <h2>What's changed</h2>
   <h3>Breaking</h3>
   <ul>
   <li><strong>SQLAlchemy 1.4 support dropped</strong> (1.4 is end-of-life; its 
last release, 1.4.54, shipped in September 2024). The supported range is now 
<code>SQLAlchemy&gt;=2.0.2,&lt;2.2</code>. The floor is 2.0.2 because version 
classes for joined-table inheritance fail to map on 2.0.0 and 2.0.1. Installs 
on SQLAlchemy 1.4 keep resolving to SQLAlchemy-Continuum 1.9.x.</li>
   <li><code>RelationshipBuilder.process_query()</code> is removed.</li>
   <li>The version fetchers' <code>previous_query()</code> and 
<code>next_query()</code> return a <code>Select</code> instead of a 
<code>Query</code>; run them with <code>session.scalars()</code>.</li>
   </ul>
   <h3>Added</h3>
   <ul>
   <li><strong>SQLModel support.</strong> SQLModel table models can be 
versioned the same way as plain SQLAlchemy models, without adding a dependency 
on SQLModel (<a 
href="https://redirect.github.com/sqlalchemy-continuum/sqlalchemy-continuum/issues/271";>#271</a>).
 See the <a 
href="https://sqlalchemy-continuum.github.io/sqlmodel/";>SQLModel</a> docs 
page.</li>
   </ul>
   <h3>Changed</h3>
   <ul>
   <li>Version lookups (<code>previous</code>, <code>next</code>, 
<code>index</code>, <code>version_at()</code>, <code>all_versions()</code>), 
version relationships, <code>changed_entities</code>, <code>vacuum()</code>, 
<code>count_versions()</code> and <code>ActivityPlugin</code> use 2.0-style 
<code>select()</code> instead of the legacy <code>Query</code> API, so SQLModel 
sessions no longer warn about them. Results are unchanged, and dynamic 
relationships such as <code>versions</code> still return a 
<code>Query</code>.</li>
   <li>CI tests SQLAlchemy 2.0 and 2.1 on Python 3.11 through 3.15, on SQLite, 
PostgreSQL (including native versioning) and MySQL.</li>
   </ul>
   <h3>Upgrading to 2.0</h3>
   <ul>
   <li>Move your project to SQLAlchemy 2.0.2 or newer first; until then, pin 
<code>SQLAlchemy-Continuum&lt;2</code>. Version tables and the transaction 
table are unchanged, so no database migration is needed.</li>
   </ul>
   <p><strong>Full changelog</strong>: <a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/compare/1.9.0...2.0.0";>https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/compare/1.9.0...2.0.0</a></p>
   <h2>1.9.0</h2>
   <h2>What's changed</h2>
   <h3>Breaking</h3>
   <ul>
   <li><strong>Python 3.10 support dropped</strong> (3.10 reached end-of-life 
on October 1, 2026). The minimum supported Python is now 3.11. Installs on 
Python 3.10 keep resolving to SQLAlchemy-Continuum 1.8.0.</li>
   </ul>
   <h3>Added</h3>
   <ul>
   <li><strong>Python 3.15 support.</strong> CI runs the test suite on Python 
3.11 through 3.15 against SQLAlchemy 1.4, 2.0 and 2.1, on SQLite, PostgreSQL 
(including native versioning) and MySQL.</li>
   </ul>
   <h3>Changed</h3>
   <ul>
   <li>Updated ruff to 0.17, which also formats the code examples in the 
documentation.</li>
   </ul>
   <p><strong>Full changelog</strong>: <a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/compare/1.8.0...1.9.0";>https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/compare/1.8.0...1.9.0</a></p>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/blob/main/docs/changelog.md";>sqlalchemy-continuum's
 changelog</a>.</em></p>
   <blockquote>
   <h2>2.0.0 (2026-10-14)</h2>
   <ul>
   <li>Drop SQLAlchemy 1.4 support (EOL; its last release, 1.4.54, shipped in 
September 2024); the supported range is now <code>&gt;=2.0.2,&lt;2.2</code>. 
Projects still on SQLAlchemy 1.4 can stay on SQLAlchemy-Continuum 1.9.x</li>
   <li>Add support for versioning <a 
href="https://sqlmodel.tiangolo.com";>SQLModel</a> table models (<a 
href="https://redirect.github.com/sqlalchemy-continuum/sqlalchemy-continuum/issues/271";>#271</a>)</li>
   <li>Use 2.0-style <code>select()</code> instead of the legacy 
<code>Query</code> API for version lookups (<code>previous</code>, 
<code>next</code>, <code>index</code>, <code>version_at()</code>, 
<code>all_versions()</code>), version relationships, 
<code>changed_entities</code>, <code>vacuum()</code>, 
<code>count_versions()</code> and <code>ActivityPlugin</code>, so SQLModel 
sessions no longer warn about them. Dynamic relationships such as 
<code>versions</code> still return a <code>Query</code>. 
<code>RelationshipBuilder.process_query()</code> is removed, and the fetchers' 
<code>previous_query()</code> and <code>next_query()</code> now return a 
<code>Select</code> instead of a <code>Query</code></li>
   </ul>
   <h2>1.9.0 (2026-10-13)</h2>
   <ul>
   <li>Drop Python 3.10 support (EOL October 2026); the minimum supported 
Python is now 3.11</li>
   <li>Add Python 3.15 support</li>
   <li>Update ruff to 0.17, which also formats the code examples in the 
documentation</li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/commit/8596b234e474ee59e140ee546b06a9089f33c3f0";><code>8596b23</code></a>
 Bump version to 2.0.0</li>
   <li><a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/commit/ee48ba34f9cd89408d058e902bff5f357145b029";><code>ee48ba3</code></a>
 Merge pull request <a 
href="https://redirect.github.com/sqlalchemy-continuum/sqlalchemy-continuum/issues/411";>#411</a>
 from sqlalchemy-continuum/feat/drop-sqlalchemy-1.4</li>
   <li><a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/commit/a1cc424691a26e1fd17143147a80fea2783e5234";><code>a1cc424</code></a>
 Make version relationship results unique, as Query.all() did</li>
   <li><a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/commit/7c8ac5737a02fd78ba872b41002cc144d67607e3";><code>7c8ac57</code></a>
 Pass the matrix Python to uv run in CI</li>
   <li><a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/commit/e5053a4e694f86d2796334bb041728a1561cb83c";><code>e5053a4</code></a>
 Replace legacy Query usage with 2.0-style select()</li>
   <li><a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/commit/40f6c1e8395d7e4363f4809d51d31c6fa94d2cbf";><code>40f6c1e</code></a>
 Drop support for SQLAlchemy 1.4</li>
   <li><a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/commit/b9cf96200a49979a8a2e2d5b4d95320d52ce13c3";><code>b9cf962</code></a>
 Merge pull request <a 
href="https://redirect.github.com/sqlalchemy-continuum/sqlalchemy-continuum/issues/410";>#410</a>
 from sqlalchemy-continuum/feat/sqlmodel-support</li>
   <li><a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/commit/8ea5cda2851d94a17345733d23b195b2a78988ab";><code>8ea5cda</code></a>
 Test the documented SQLModel setup on the default registry</li>
   <li><a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/commit/c7f3645b4719f0eb1db72a085bb589c8f14bcf68";><code>c7f3645</code></a>
 Add support for versioning SQLModel models</li>
   <li><a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/commit/caaed638cafbe83ed3c489f5fc76d2ea0ec307c8";><code>caaed63</code></a>
 Bump version to 1.9.0</li>
   <li>Additional commits viewable in <a 
href="https://github.com/sqlalchemy-continuum/sqlalchemy-continuum/compare/1.8.0...2.0.0";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=sqlalchemy-continuum&package-manager=pip&previous-version=1.8.0&new-version=2.0.0)](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: [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]

Reply via email to