Bump pytest-mock from 3.3.1 to 3.14.1

[dependabot]

Bumps pytest-mock from 3.3.1 to 3.14.1.

Release notes

Sourced from pytest-mock's releases.

v3.14.1

• #503: Python 3.14 is now officially supported.

v3.14.0

• #415: MockType and AsyncMockType can be imported from pytest_mock for type annotation purposes.
• #420: Fixed a regression which would cause mocker.patch.object to not being properly cleared between tests.

v3.13.0

• #417: spy now has spy_return_list, which is a list containing all the values returned by the spied function.
• pytest-mock now requires pytest>=6.2.5.
• #410: pytest-mock's setup.py file is removed. If you relied on this file, e.g. to install pytest using setup.py install, please see Why you shouldn't invoke setup.py directly for alternatives.

v3.12.0

• Added support for Python 3.12.
• Dropped support for EOL Python 3.7.
• mocker.resetall() now also resets mocks created by mocker.create_autospec (#390).

v3.11.1

• Fixed introspection for failed assert_has_calls (#365).

• Updated type annotations for mocker.patch and mocker.spy (#364).

v3.10.0

• Added new mocker.stop(m) method to stop specific mocker.patch or mocker.spy calls (#319).

v3.9.0

• Expose NonCallableMagicMock via the mocker fixture (#318).

v3.8.2

• Fixed AsyncMock support for Python 3.7+ in mocker.async_stub (#302).

v3.8.1

• Fix regression caused by an explicit mock dependency in the code (#298).

v3.8.0

• Add MockerFixture.async_mock method. Thanks @​PerchunPak for the PR (#296).

3.7.0

• Python 3.10 now officially supported.
• Dropped support for Python 3.6.

3.6.1 (2021-05-06)

• Fix mocker.resetall() when using mocker.spy() (#237). Thanks @​blaxter for the report and @​shadycuz for the PR.

... (truncated)

Changelog

Sourced from pytest-mock's changelog.

3.14.1 (2025-08-26)

• [#503](https://github.com/pytest-dev/pytest-mock/issues/503) <https://github.com/pytest-dev/pytest-mock/pull/503>_: Python 3.14 is now officially supported.

3.14.0 (2024-03-21)

• [#415](https://github.com/pytest-dev/pytest-mock/issues/415) <https://github.com/pytest-dev/pytest-mock/pull/415>_: MockType and AsyncMockType can be imported from pytest_mock for type annotation purposes.

• [#420](https://github.com/pytest-dev/pytest-mock/issues/420) <https://github.com/pytest-dev/pytest-mock/issues/420>_: Fixed a regression which would cause mocker.patch.object to not being properly cleared between tests.

3.13.0 (2024-03-21)

• [#417](https://github.com/pytest-dev/pytest-mock/issues/417) <https://github.com/pytest-dev/pytest-mock/pull/417>_: spy now has spy_return_list, which is a list containing all the values returned by the spied function.
• pytest-mock now requires pytest>=6.2.5.
• [#410](https://github.com/pytest-dev/pytest-mock/issues/410) <https://github.com/pytest-dev/pytest-mock/pull/410>: pytest-mock's setup.py file is removed. If you relied on this file, e.g. to install pytest using setup.py install, please see Why you shouldn't invoke setup.py directly <https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html#summary> for alternatives.

3.12.0 (2023-10-19)

• Added support for Python 3.12.
• Dropped support for EOL Python 3.7.
• mocker.resetall() now also resets mocks created by mocker.create_autospec ([#390](https://github.com/pytest-dev/pytest-mock/issues/390)_).

.. _#390: pytest-dev/pytest-mock#390

3.11.1 (2023-06-15)

(This release source code is identical to 3.11.0 except a small internal fix to deployment/CI)

• Fixed introspection for failed assert_has_calls ([#365](https://github.com/pytest-dev/pytest-mock/issues/365)_).

• Updated type annotations for mocker.patch and mocker.spy ([#364](https://github.com/pytest-dev/pytest-mock/issues/364)_).

.. _#365: pytest-dev/pytest-mock#365 .. _#364: pytest-dev/pytest-mock#364

3.11.0 (2023-06-15)

• Fixed introspection for failed assert_has_calls ([#365](https://github.com/pytest-dev/pytest-mock/issues/365)_).

• Updated type annotations for mocker.patch and mocker.spy ([#364](https://github.com/pytest-dev/pytest-mock/issues/364)_).

... (truncated)

Commits

• 34dd61a Release 3.14.1
• 299adb9 Add support for Python 3.14 (#503)
• f5fcef7 [pre-commit.ci] pre-commit autoupdate (#504)
• bae64d8 [pre-commit.ci] pre-commit autoupdate (#502)
• 824f334 [pre-commit.ci] pre-commit autoupdate (#501)
• db1add6 [pre-commit.ci] pre-commit autoupdate (#500)
• 48ac874 [pre-commit.ci] pre-commit autoupdate (#499)
• fe7ad9a [pre-commit.ci] pre-commit autoupdate (#498)
• 7857e60 [pre-commit.ci] pre-commit autoupdate (#497)
• a8b97ea [pre-commit.ci] pre-commit autoupdate (#496)
• 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 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)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[dependabot]

Superseded by #739.