[dependabot]

Bumps the python-minor-and-patch group with 3 updates: sqlalchemy, fastapi and pytest-mock.

Updates sqlalchemy from 2.0.54 to 2.0.55

Release notes

Sourced from sqlalchemy's releases.

2.0.55

Released: October 16, 2026

orm

• [orm] [bug] Fixed issue in Annotated Declarative where an annotation naming an undefined symbol, where the annotation is not wrapped in _orm.Mapped, would raise TypeError rather than the expected MappedAnnotationError when running under Python 3.14 without from __future__ import annotations in effect. Under PEP 649, such an annotation is delivered as a ForwardRef rather than a string, a form which was not accommodated by the check that determines whether an unresolvable annotation was intended to be mapped.

  References: #13602

• [orm] [bug] [regression] Fixed regression caused by #11917 in version 2.0.36 where an ORM enabled _sql.update() using WHERE criteria which matched more than one object present in the _orm.Session would expire server-side onupdate columns, as well as columns that were SET to a SQL expression, on only one of the matched objects, leaving the remaining objects with stale values for those attributes. The columns are now expired for all matched objects.

  References: #13675

orm extensions

• [bug] [orm extensions] Fixed issue in the mutable_toplevel extension where the in-place |= operator on MutableDict and the in-place *= operator on MutableList did not emit change events, so that the modification was not detected and was not persisted on the next flush. These operators now invoke Mutable.changed() in the same way as the in-place set operators of MutableSet and the += operator of MutableList.

  References: #13643

engine

• [engine] [bug] [regression] Fixed regression from the 1.4 series where the DBAPI cursor used for a compiled statement that returns no rows, which includes DDL constructs such as CreateTable and DropTable as well as the SAVEPOINT, ROLLBACK TO SAVEPOINT and RELEASE SAVEPOINT statements emitted by _engine.Connection.begin_nested(), was not closed after execution, and was instead left to be released when garbage collected.

... (truncated)

Commits

• See full diff in compare view

Updates fastapi from 0.143.3 to 0.146.0

Release notes

Sourced from fastapi's releases.

0.146.0

The root_path parameter in FastAPI() is deprecated. Configure the server with fastapi run --root-path /api/v1 instead.

Breaking Changes

• 🗑️ Deprecate the root_path parameter in FastAPI. PR #16520 by @​tiangolo.

0.145.0

Breaking Changes

• 🔥 Remove deprecated openapi_prefix and unused **extra from FastAPI. PR #16518 by @​tiangolo.

Docs

• 📝 Document URL paths in templates. PR #16517 by @​tiangolo.

0.144.0

Features

• ✨ Add WebSocket support to security dependencies. PR #10147 by @​mnixry.

0.143.5

Fixes

• 🐛 Fix handling of empty value for byte file list parameter. PR #9383 by @​Viicos.

0.143.4

Upgrades

• ⬆️ Add httpx2 to optional dependencies. PR #16512 by @​tiangolo.

Commits

• 3070b51 🔖 Release version 0.146.0 (#16521)
• a17bd59 📝 Update release notes
• 45c4199 🗑️ Deprecate the root_path parameter in FastAPI (#16520)
• 129c9cf 🔖 Release version 0.145.0 (#16519)
• 475b466 📝 Update release notes
• a37a162 🔥 Remove deprecated openapi_prefix and unused **extra from FastAPI (#16...
• 0ab3e03 📝 Update release notes
• 4f940b1 📝 Document URL paths in templates (#16517)
• 9528746 🔖 Release version 0.144.0 (#16516)
• c18732c 📝 Update release notes
• Additional commits viewable in compare view

Updates pytest-mock from 3.16.0 to 3.17.0

Release notes

Sourced from pytest-mock's releases.

v3.17.0

2026-10-17

• #641: Failures of mock assertions such as assert_called_with are again reported only once, instead of two or three times with the original error from the mock module chained before them.
• #642: Mock assertion failures no longer show misleading introspection when they are not about the arguments of the last call: assert_called, assert_called_once, assert_not_called, assert_any_call, their await counterparts, and assert_called_once_with/assert_awaited_once_with when the mock was not called (awaited) exactly once. The introspection also no longer reports arguments passed by position versus by keyword as different for autospecced mocks, and no longer shows empty Args:/Kwargs: sections when assertion rewriting is not available.
• #643: assert_has_calls and assert_has_awaits failures no longer show pytest introspection, which compared the expected and actual calls position by position and so reported differences between unrelated calls. The mock's own message, listing the expected and actual calls, is still shown.

v3.16.1

2026-10-17

• #617: Fixed assert_has_calls raising ValueError instead of AssertionError (or showing misleading introspection) when the expected calls are plain tuples rather than call(...) objects, such as (args, kwargs) entries of another mock's call_args_list, (args,), (kwargs,), (name, args) or (name, kwargs).
• #621: Fixed mocker.stop() sometimes stopping the wrong mock, for example with mocks from mocker.create_autospec.
• #621: mocker.stop() now undoes the most recent patch first when the same object is used in several patches.
• #623: Fixed misleading introspection in assert_has_awaits failures, and assert_has_calls/assert_has_awaits raising IndexError instead of AssertionError when calls is passed by keyword.
• #624: Clear spy_return_iter after a spied synchronous or asynchronous function raises, matching spy_return.
• #627: Document async_stub await assertions and the distinction between call and await tracking.
• #629: Fixed mocker.resetall() skipping the mocks patched with mocker.patch.multiple(), both the ones it creates and the ones passed explicitly.
• #630: mocker.resetall() now also resets spy_return and spy_exception of spies, like it already did for spy_return_list and spy_return_iter, and no longer overwrites attributes with these names on mocks that are not spies.
• #633: Fixed spies on classmethod, staticmethod, builtins and classes returning a MagicMock instead of calling the spied code after mocker.resetall(side_effect=True). Resetting a spy's side_effect now goes back to calling the spied code, also clearing any side_effect set on the spy.

Changelog

Sourced from pytest-mock's changelog.

3.17.0

2026-10-17

• [#641](https://github.com/pytest-dev/pytest-mock/issues/641) <https://github.com/pytest-dev/pytest-mock/pull/641>_: Failures of mock assertions such as assert_called_with are again reported only once, instead of two or three times with the original error from the mock module chained before them.
• [#642](https://github.com/pytest-dev/pytest-mock/issues/642) <https://github.com/pytest-dev/pytest-mock/pull/642>_: Mock assertion failures no longer show misleading introspection when they are not about the arguments of the last call: assert_called, assert_called_once, assert_not_called, assert_any_call, their await counterparts, and assert_called_once_with/assert_awaited_once_with when the mock was not called (awaited) exactly once. The introspection also no longer reports arguments passed by position versus by keyword as different for autospecced mocks, and no longer shows empty Args:/Kwargs: sections when assertion rewriting is not available.
• [#643](https://github.com/pytest-dev/pytest-mock/issues/643) <https://github.com/pytest-dev/pytest-mock/pull/643>_: assert_has_calls and assert_has_awaits failures no longer show pytest introspection, which compared the expected and actual calls position by position and so reported differences between unrelated calls. The mock's own message, listing the expected and actual calls, is still shown.

3.16.1

2026-10-17

• [#617](https://github.com/pytest-dev/pytest-mock/issues/617) <https://github.com/pytest-dev/pytest-mock/pull/617>_: Fixed assert_has_calls raising ValueError instead of AssertionError (or showing misleading introspection) when the expected calls are plain tuples rather than call(...) objects, such as (args, kwargs) entries of another mock's call_args_list, (args,), (kwargs,), (name, args) or (name, kwargs).
• [#621](https://github.com/pytest-dev/pytest-mock/issues/621) <https://github.com/pytest-dev/pytest-mock/pull/621>_: Fixed mocker.stop() sometimes stopping the wrong mock, for example with mocks from mocker.create_autospec.
• [#621](https://github.com/pytest-dev/pytest-mock/issues/621) <https://github.com/pytest-dev/pytest-mock/pull/621>_: mocker.stop() now undoes the most recent patch first when the same object is used in several patches.
• [#623](https://github.com/pytest-dev/pytest-mock/issues/623) <https://github.com/pytest-dev/pytest-mock/pull/623>_: Fixed misleading introspection in assert_has_awaits failures, and assert_has_calls/assert_has_awaits raising IndexError instead of AssertionError when calls is passed by keyword.
• [#624](https://github.com/pytest-dev/pytest-mock/issues/624) <https://github.com/pytest-dev/pytest-mock/pull/624>_: Clear spy_return_iter after a spied synchronous or asynchronous function raises, matching spy_return.
• [#627](https://github.com/pytest-dev/pytest-mock/issues/627) <https://github.com/pytest-dev/pytest-mock/pull/627>_: Document async_stub await assertions and the distinction between call and await tracking.
• [#629](https://github.com/pytest-dev/pytest-mock/issues/629) <https://github.com/pytest-dev/pytest-mock/pull/629>_: Fixed mocker.resetall() skipping the mocks patched with mocker.patch.multiple(), both the ones it creates and the ones passed explicitly.
• [#630](https://github.com/pytest-dev/pytest-mock/issues/630) <https://github.com/pytest-dev/pytest-mock/pull/630>_: mocker.resetall() now also resets spy_return and spy_exception of spies, like it already did for spy_return_list and spy_return_iter, and no longer overwrites attributes with these names on mocks that are not spies.
• [#633](https://github.com/pytest-dev/pytest-mock/issues/633) <https://github.com/pytest-dev/pytest-mock/pull/633>_: Fixed spies on classmethod, staticmethod, builtins and classes returning a MagicMock instead of calling the spied code after mocker.resetall(side_effect=True). Resetting a spy's side_effect now goes back to calling the spied code, also clearing any side_effect set on the spy.

Commits

• 5c2f207 Release 3.17.0
• 9625271 Bump the minor version for releases that change existing behavior
• 34b87ae Drop introspection from assert_has_calls and assert_has_awaits (#643)
• 866520f Only show introspection for failures about the call arguments (#642)
• 5ab41c1 Do not chain the original mock error to wrapped assertion failures (#641)
• 1916b14 Merge pull request #635 from nicoddemus/docs-contributing-resetall
• 212fcd9 Document resetall, the changelog format and running tests with tox
• 9374b2c Merge pull request #634 from pytest-dev/release-3.16.1
• fab730d Release 3.16.1
• d26d41b Merge pull request #627 from xiehuanyi/docs/async-stub-awaits-20261012-r2
• Additional commits viewable 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.