chore(api): bump sqlalchemy from 1.4.44 to 2.0.29 in /api

[dependabot[bot]]

Bumps sqlalchemy from 1.4.44 to 2.0.29.

Release notes

Sourced from sqlalchemy's releases.

2.0.29

Released: March 23, 2024

orm

• [orm] [usecase] Added support for the PEP 695 TypeAliasType construct as well as the python 3.12 native type keyword to work with ORM Annotated Declarative form when using these constructs to link to a PEP 593 Annotated container, allowing the resolution of the Annotated to proceed when these constructs are used in a _orm.Mapped typing container.

  References: #11130

• [orm] [bug] Fixed Declarative issue where typing a relationship using _orm.Relationship rather than _orm.Mapped would inadvertently pull in the "dynamic" relationship loader strategy for that attribute.

  References: #10611

• [orm] [bug] Fixed issue in ORM annotated declarative where using _orm.mapped_column() with an _orm.mapped_column.index or _orm.mapped_column.unique setting of False would be overridden by an incoming Annotated element that featured that parameter set to True, even though the immediate _orm.mapped_column() element is more specific and should take precedence. The logic to reconcile the booleans has been enhanced to accommodate a local value of False as still taking precedence over an incoming True value from the annotated element.

  References: #11091

• [orm] [bug] [regression] Fixed regression from version 2.0.28 caused by the fix for #11085 where the newer method of adjusting post-cache bound parameter values would interefere with the implementation for the _orm.subqueryload() loader option, which has some more legacy patterns in use internally, when the additional loader criteria feature were used with this loader option.

  References: #11173

engine

• [engine] [bug] Fixed issue in engine_insertmanyvalues feature where using a primary key column with an "inline execute" default generator such as an explicit Sequence with an explcit schema name, while at the same time using the _engine.Connection.execution_options.schema_translate_map

... (truncated)

Commits

• See full diff in compare view

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 commands and options

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 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)

[ahal]

Here's a sqlalchemy 2.0 migration guide: https://docs.sqlalchemy.org/en/20/changelog/migration_20.html

Sounds like this might be a small bit of work. We may want to file an issue (like we did for connexion and then disable this for dependabot (and connexion).

[dependabot[bot]]

Superseded by #1456.