build(deps): bump the all-dependencies group across 1 directory with 3 updates

[dependabot]

Bumps the all-dependencies group with 3 updates in the /historian directory: pika, sqlalchemy and pytest-rerunfailures.

Updates pika from 1.4.0 to 1.4.1

Release notes

Sourced from pika's releases.

1.4.1

https://pypi.org/project/pika/1.4.1/ | GitHub milestone

Changelog

Sourced from pika's changelog.

1.4.1 (2026-05-22)

Merged pull requests:

• Fix Channel.close() for channels with multiple consumers #1596 (gbenson)

Commits

• 5f0ba9e Merge pull request #1597 from pika/pika-1.4.1
• 31d80a9 pika 1.4.1
• b7af301 Merge pull request #1596 from gbenson/main
• See full diff in compare view

Updates sqlalchemy from 2.0.49 to 2.0.51

Release notes

Sourced from sqlalchemy's releases.

2.0.51

Released: June 15, 2026

orm

• [orm] [bug] Fixed issue where _orm.subqueryload() combined with PropComparator.of_type() and PropComparator.and_() would silently drop the additional filter criteria, causing all related objects to be loaded instead of only those matching the filter. The LoaderCriteriaOption was being constructed against the base entity rather than the effective entity indicated by PropComparator.of_type(). Pull request courtesy Arya Rizky.

  References: #13207

• [orm] [bug] Fixed bug where a failure during tpc_prepare() within _orm.Session.commit() for a two-phase session would raise IllegalStateChangeError instead of the original database exception. The internal _prepare_impl() method's error handler was unable to invoke _orm.SessionTransaction.rollback() due to a state-change guard, preventing proper cleanup and masking the underlying error.

  References: #13356

engine

• [engine] [bug] Fixed issue where Result.freeze() would lose track of ambiguous column names present in the original CursorResult, causing key-based access on the thawed result to silently return a value instead of raising InvalidRequestError. The SimpleResultMetaData now accepts and propagates ambiguous key information so that frozen, thawed, and pickled results raise consistently for duplicate column names. Pull request courtesy Saurabh Kohli.

  References: #9427

sql

• [sql] [bug] Fixed issue where _sql.StatementLambdaElement would proxy attribute access through the cached "expected" expression rather than the resolved expression, causing stale closure-bound parameter values to be used when a lambda statement was extended with non-lambda criteria such as an additional .where() clause. Courtesy cjc0013.

  References: #10827

... (truncated)

Commits

• See full diff in compare view

Updates pytest-rerunfailures from 16.2 to 16.3

Changelog

Sourced from pytest-rerunfailures's changelog.

16.3 (2026-05-22)

Features ++++++++

• Add --reruns-mode option (strict or append). With append, marker reruns and the global --reruns / reruns ini setting are summed instead of the marker taking strict priority. Default is strict so existing behaviour is unchanged. Fixes [#321](https://github.com/pytest-dev/pytest-rerunfailures/issues/321) <https://github.com/pytest-dev/pytest-rerunfailures/issues/321>_.

• Add --rerun-show-tracebacks option to display tracebacks from failed attempts that were retried, including tests that eventually passed. The rerun summary section is emitted automatically when the flag is set, so -rR is no longer required to see the tracebacks. Fixes [#156](https://github.com/pytest-dev/pytest-rerunfailures/issues/156) <https://github.com/pytest-dev/pytest-rerunfailures/issues/156>_.

Commits

• 4b3a220 Preparing release 16.3
• d17f3be feat: add --reruns-mode option to sum marker and global reruns (#321) (#328)
• 4a00fac Add --rerun-show-tracebacks to surface retried failures (#329)
• 9f792d9 Back to development: 16.3
• See full diff in compare view