Build(deps): Bump the python-runtime group across 1 directory with 3 updates

[dependabot]

Bumps the python-runtime group with 3 updates in the /backend directory: langsmith, openai and sqlalchemy.

Updates langsmith from 0.14.3 to 0.14.4

Release notes

Sourced from langsmith's releases.

v0.14.4

What's Changed

• release(js): 0.10.7 by @​KiewanVillatel in langchain-ai/langsmith-sdk#3647
• ci: request Open SWE investigation of nightly SDK failures by @​thibautlehmann in langchain-ai/langsmith-sdk#3649
• refactor: take addresses as strings (Python and JS) by @​KiewanVillatel in langchain-ai/langsmith-sdk#3651
• fix(py,js): correctly resolve the full OTLP traces endpoint by @​emil-lc in langchain-ai/langsmith-sdk#3645
• release(py): 0.14.4 by @​KiewanVillatel in langchain-ai/langsmith-sdk#3652

Full Changelog: langchain-ai/langsmith-sdk@v0.14.3...v0.14.4

Commits

• a39745c release(py): 0.14.4 (#3652)
• 6e96ab4 fix(py,js): correctly resolve the full OTLP traces endpoint (#3645)
• b1fa054 refactor: take addresses as strings (Python and JS) (#3651)
• 1322234 ci: request Open SWE investigation of nightly SDK failures (#3649)
• ff34d38 release(js): 0.10.7 (#3647)
• See full diff in compare view

Updates openai from 3.23.0 to 3.24.0

Release notes

Sourced from openai's releases.

v3.24.0

3.24.0 (2026-10-02)

Features

• api: add custom voice creation and agent session events (#4013) (e5de2e5)

Bug Fixes

• api: prioritize Python request routing fields (#4014) (ffcc4c4)
• api: prioritize routing fields in parse helpers (#4016) (ba53a10)

Changelog

Sourced from openai's changelog.

3.24.0 (2026-10-02)

Features

• api: add custom voice creation and agent session events (#4013) (e5de2e5)

Bug Fixes

• api: prioritize Python request routing fields (#4014) (ffcc4c4)
• api: prioritize routing fields in parse helpers (#4016) (ba53a10)

Commits

• 637f1b8 release: 3.24.0 (#4015)
• e5de2e5 feat(api): add custom voice creation and agent session events (#4013)
• ba53a10 fix(api): prioritize routing fields in parse helpers (#4016)
• ffcc4c4 fix(api): prioritize Python request routing fields (#4014)
• See full diff in compare view

Updates sqlalchemy from 2.1.1 to 2.1.2

Release notes

Sourced from sqlalchemy's releases.

2.1.2

Released: October 2, 2026

orm

• [orm] [bug] [regression] Fixed regression caused by #5987 where the selectinload() loader strategy would ignore additional criteria present in the _orm.relationship.primaryjoin of a many-to-many relationship, such as a comparison against a column on the association table or on the parent table, loading related rows that should have been excluded. The omit_join optimization for many-to-many relationships is now only used when the primaryjoin consists solely of comparisons between the parent's primary key columns and the association table.

  References: #13626

engine

• [engine] [bug] [regression] Fixed regression where result rows delivered by the DBAPI as a subclass of tuple would fail to be processed when the Cython extensions were in use, raising TypeError: Expected tuple. Such rows are now converted to a plain tuple, as was the case in 2.0. Rows delivered as a plain tuple, or as a sequence that is not a tuple at all such as asyncpg's Record, were not affected. Drivers such as the Databricks SQL connector return rows that are tuple subclasses.

  References: #13619

sql

• [sql] [bug] The plain string portions of a _sql.tstring() construct are no longer scanned for bound parameter names in the :name format, and no longer interpret the \: escape sequence; the text is now rendered exactly as given. Previously, each string portion was parsed in the same way as _sql.text(), so that a colon within a quoted SQL string, such as 'time is :now', would be rendered as a bound parameter, failing at execution time.

  This change is a breaking change in the behavior of the newly introduced _sql.tstring() feature, as the former use of text() inadvertently provided a behavior that wasn't intended. In order to embed an explicit parameter in the SQL generated by _sql.tstring(), _sql.bindparam() may be used directly, e.g. tstring(t"SELECT {bindparam('p')}").

  References: #13616

... (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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.