Commit e9880ca
authored
Build: Bump sqlalchemy from 2.0.44 to 2.0.45 (#2836)
Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.44
to 2.0.45.
<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.45</h1>
<p>Released: December 9, 2025</p>
<h2>orm</h2>
<ul>
<li>
<p><strong>[orm] [bug]</strong> Fixed issue where calling
<code>Mapper.add_property()</code> within mapper event
hooks such as <code>MapperEvents.instrument_class()</code>,
<code>MapperEvents.after_mapper_constructed()</code>, or
<code>MapperEvents.before_mapper_configured()</code> would raise an
<code>AttributeError</code> because the mapper's internal property
collections were
not yet initialized. The <code>Mapper.add_property()</code> method now
handles
early-stage property additions correctly, allowing properties including
column properties, deferred columns, and relationships to be added
during
mapper initialization events. Pull request courtesy G Allajmi.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/12858">#12858</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Fixed issue in Python 3.14 where
dataclass transformation would fail when
a mapped class using <code>MappedAsDataclass</code> included a
<code>relationship()</code> referencing a class that was not available
at
runtime (e.g., within a <code>TYPE_CHECKING</code> block). This occurred
when using
Python 3.14's <a href="https://peps.python.org/pep-0649">PEP 649</a>
deferred annotations feature, which is the
default behavior without a <code>from __future__ import
annotations</code>
directive.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/12952">#12952</a></p>
</li>
</ul>
<h2>examples</h2>
<ul>
<li><strong>[examples] [bug]</strong> Fixed the
"short_selects" performance example where the cache was being
used in all the examples, making it impossible to compare performance
with
and without the cache. Less important comparisons like
"lambdas" and
"baked queries" have been removed.</li>
</ul>
<h2>sql</h2>
<ul>
<li>
<p><strong>[sql] [bug]</strong> Some improvements to the
<code>_sql.ClauseElement.params()</code> method to
replace bound parameters in a query were made, however the ultimate
issue
in <a href="https://www.sqlalchemy.org/trac/ticket/12915">#12915</a>
involving ORM <code>_orm.aliased()</code> cannot be fixed fully
until 2.1, where the method is being rewritten to work without relying
on
Core cloned traversal.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/12915">#12915</a></p>
</li>
<li>
<p><strong>[sql] [bug]</strong> Fixed issue where using the
<code>ColumnOperators.in_()</code> operator with a
nested <code>CompoundSelect</code> statement (e.g. an
<code>INTERSECT</code> of
<code>UNION</code> queries) would raise a
<code>NotImplementedError</code> when the</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 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>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>1 parent b4bd329 commit e9880ca
1 file changed
+40
-36
lines changed
0 commit comments