dependabot[bot] opened a new pull request, #1502: URL: https://github.com/apache/iceberg-python/pull/1502
Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.36 to 2.0.37. <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.37</h1> <p>Released: January 9, 2025</p> <h2>orm</h2> <ul> <li> <p><strong>[orm] [bug]</strong> Fixed issue regarding <code>Union</code> types that would be present in the <code>_orm.registry.type_annotation_map</code> of a <code>_orm.registry</code> or declarative base class, where a <code>Mapped</code> element that included one of the subtypes present in that <code>Union</code> would be matched to that entry, potentially ignoring other entries that matched exactly. The correct behavior now takes place such that an entry should only match in <code>_orm.registry.type_annotation_map</code> exactly, as a <code>Union</code> type is a self-contained type. For example, an attribute with <code>Mapped[float]</code> would previously match to a <code>_orm.registry.type_annotation_map</code> entry <code>Union[float, Decimal]</code>; this will no longer match and will now only match to an entry that states <code>float</code>. Pull request courtesy Frazer McLean.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/11370";>#11370</a></p> </li> <li> <p><strong>[orm] [bug]</strong> Fixed bug in how type unions were handled within <code>_orm.registry.type_annotation_map</code> as well as <code>_orm.Mapped</code> that made the lookup behavior of <code>a | b</code> different from that of <code>Union[a, b]</code>.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/11944";>#11944</a></p> </li> <li> <p><strong>[orm] [bug]</strong> Consistently handle <code>TypeAliasType</code> (defined in PEP 695) obtained with the <code>type X = int</code> syntax introduced in python 3.12. Now in all cases one such alias must be explicitly added to the type map for it to be usable inside <code>Mapped</code>. This change also revises the approach added in <a href="https://www.sqlalchemy.org/trac/ticket/11305";>#11305</a>, now requiring the <code>TypeAliasType</code> to be added to the type map. Documentation on how unions and type alias types are handled by SQLAlchemy has been added in the <code>orm_declarative_mapped_column_type_map</code> section of the documentation.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/11955";>#11955</a></p> </li> <li> <p><strong>[orm] [bug]</strong> Fixed regression caused by an internal code change in response to recent Mypy releases that caused the very unusual case of a list of ORM-mapped attribute expressions passed to <code>ColumnOperators.in_()</code> to no longer be accepted.</p> <p>References: <a href="https://www.sqlalchemy.org/trac/ticket/12019";>#12019</a></p> </li> <li> <p><strong>[orm] [bug]</strong> Fixed issues in type handling within the <code>_orm.registry.type_annotation_map</code> feature which prevented the use of unions, using either pep-604 or <code>Union</code> syntaxes under future</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> -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
