Skip to content

Commit 3c96e0b

Browse files
dependabot[bot]inmantaci
authored andcommitted
Bump sqlalchemy from 2.0.41 to 2.0.42 (PR #9395)
Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.41 to 2.0.42. <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.42</h1> <p>Released: July 29, 2025</p> <h2>orm</h2> <ul> <li> <p><strong>[orm] [usecase]</strong> Added <code>dataclass_metadata</code> argument to all ORM attribute constructors that accept dataclasses parameters, e.g. <code>mapped_column.dataclass_metadata</code>, <code>relationship.dataclass_metadata</code>, etc. It's passed to the underlying dataclass <code>metadata</code> attribute of the dataclass field. Pull request courtesy Sigmund Lahn.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/10674">#10674</a></p> </li> <li> <p><strong>[orm] [bug]</strong> Implemented the <code>_orm.defer()</code>, <code>_orm.undefer()</code> and <code>_orm.load_only()</code> loader options to work for composite attributes, a use case that had never been supported previously.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/12593">#12593</a></p> </li> <li> <p><strong>[orm] [bug]</strong> Fixed bug where the ORM would pull in the wrong column into an UPDATE when a key name inside of the <code>ValuesBase.values()</code> method could be located from an ORM entity mentioned in the statement, but where that ORM entity was not the actual table that the statement was inserting or updating. An extra check for this edge case is added to avoid this problem.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/12692">#12692</a></p> </li> </ul> <h2>engine</h2> <ul> <li><strong>[engine]</strong> Improved validation of execution parameters passed to the <code>_engine.Connection.execute()</code> and similar methods to provided a better error when tuples are passed in. Previously the execution would fail with a difficult to understand error message.</li> </ul> <h2>sql</h2> <ul> <li> <p><strong>[sql] [usecase]</strong> The <code>_sql.values()</code> construct gains a new method <code>_sql.Values.cte()</code>, which allows creation of a named, explicit-columns <code>CTE</code> against an unnamed <code>VALUES</code> expression, producing a syntax that allows column-oriented selection from a <code>VALUES</code> construct on modern versions of PostgreSQL, SQLite, and MariaDB.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/12734">#12734</a></p> </li> <li> <p><strong>[sql] [bug]</strong> Fixed issue where <code>select()</code> of a free-standing scalar expression that</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 /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=sqlalchemy&package-manager=pip&previous-version=2.0.41&new-version=2.0.42)](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>
1 parent 9f4916b commit 3c96e0b

File tree

2 files changed

+6
-1
lines changed

2 files changed

+6
-1
lines changed
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
change-type: patch
2+
description: Bump sqlalchemy from 2.0.41 to 2.0.42
3+
destination-branches:
4+
- master
5+
sections: {}

requirements.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ sphinxcontrib-redoc==1.6.0
4747
sphinxcontrib-serializinghtml==2.0.0
4848
sphinx-design==0.6.1
4949
Sphinx-Substitution-Extensions==2025.6.6
50-
SQLAlchemy==2.0.41
50+
SQLAlchemy==2.0.42
5151
strawberry-sqlalchemy-mapper==0.6.4
5252
texttable==1.7.0
5353
time-machine==2.16.0

0 commit comments

Comments
 (0)