dependabot[bot] opened a new pull request, #2617:
URL: https://github.com/apache/iceberg-python/pull/2617

   Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.43 to 
2.0.44.
   <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.0.44</h1>
   <p>Released: October 10, 2025</p>
   <h2>platform</h2>
   <ul>
   <li><strong>[platform] [bug]</strong> Unblocked automatic greenlet 
installation for Python 3.14 now that
   there are greenlet wheels on pypi for python 3.14.</li>
   </ul>
   <h2>orm</h2>
   <ul>
   <li>
   <p><strong>[orm] [usecase]</strong> The way ORM Annotated Declarative 
interprets Python <a href="https://peps.python.org/pep-0695";>PEP 695</a> type 
aliases
   in <code>Mapped[]</code> annotations has been refined to expand the lookup 
scheme. A
   <a href="https://peps.python.org/pep-0695";>PEP 695</a> type can now be 
resolved based on either its direct presence in
   <code>_orm.registry.type_annotation_map</code> or its immediate resolved
   value, as long as a recursive lookup across multiple <a 
href="https://peps.python.org/pep-0695";>PEP 695</a> types is
   not required for it to resolve. This change reverses part of the
   restrictions introduced in 2.0.37 as part of <a 
href="https://www.sqlalchemy.org/trac/ticket/11955";>#11955</a>, which
   deprecated (and disallowed in 2.1) the ability to resolve any <a 
href="https://peps.python.org/pep-0695";>PEP 695</a>
   type that was not explicitly present in
   <code>_orm.registry.type_annotation_map</code>. Recursive lookups of
   <a href="https://peps.python.org/pep-0695";>PEP 695</a> types remains 
deprecated in 2.0 and disallowed in version 2.1,
   as do implicit lookups of <code>NewType</code> types without an entry in
   <code>_orm.registry.type_annotation_map</code>.</p>
   <p>Additionally, new support has been added for generic <a 
href="https://peps.python.org/pep-0695";>PEP 695</a> aliases that
   refer to <a href="https://peps.python.org/pep-0593";>PEP 593</a> 
<code>Annotated</code> constructs containing
   <code>_orm.mapped_column()</code> configurations. See the sections below for
   examples.</p>
   <p>References: <a 
href="https://www.sqlalchemy.org/trac/ticket/12829";>#12829</a></p>
   </li>
   <li>
   <p><strong>[orm] [bug]</strong> Fixed a caching issue where 
<code>_orm.with_loader_criteria()</code> would
   incorrectly reuse cached bound parameter values when used with
   <code>_sql.CompoundSelect</code> constructs such as 
<code>_sql.union()</code>. The
   issue was caused by the cache key for compound selects not including the
   execution options that are part of the <code>_sql.Executable</code> base 
class,
   which <code>_orm.with_loader_criteria()</code> uses to apply its criteria
   dynamically. The fix ensures that compound selects and other executable
   constructs properly include execution options in their cache key 
traversal.</p>
   <p>References: <a 
href="https://www.sqlalchemy.org/trac/ticket/12905";>#12905</a></p>
   </li>
   </ul>
   <h2>engine</h2>
   <ul>
   <li><strong>[engine] [bug]</strong> Implemented initial support for 
free-threaded Python by adding new tests
   and reworking the test harness to include Python 3.13t and Python 3.14t 
in</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 />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=sqlalchemy&package-manager=pip&previous-version=2.0.43&new-version=2.0.44)](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 merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@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