Update dependency pytest-mock to v3.14.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pytest-mock (changelog)	==3.6.1 -> ==3.14.1

---

Release Notes

pytest-dev/pytest-mock (pytest-mock)

v3.14.1

Compare Source

• #&#8203;503 <https://github.com/pytest-dev/pytest-mock/pull/503>_: Python 3.14 is now officially supported.

v3.14.0

Compare Source

• #&#8203;415 <https://github.com/pytest-dev/pytest-mock/pull/415>_: MockType and AsyncMockType can be imported from pytest_mock for type annotation purposes.

• #&#8203;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.

v3.13.0

Compare Source

• #&#8203;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.
• #&#8203;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.

v3.12.0

Compare Source

• 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_).

.. _#390:https://github.com/pytest-dev/pytest-mock/pull/3900

v3.11.1

Compare Source

(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_).

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

.. _#365:https://github.com/pytest-dev/pytest-mock/pull/3655
.. _#364https://github.com/pytest-dev/pytest-mock/pull/36464

v3.11.0

Compare Source

• Fixed introspection for failed assert_has_calls (#365_).

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

.. _#365:https://github.com/pytest-dev/pytest-mock/pull/3655
.. _#364https://github.com/pytest-dev/pytest-mock/pull/36464

v3.10.0

Compare Source

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

.. _#319:https://github.com/pytest-dev/pytest-mock/pull/3199

v3.9.0

Compare Source

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

.. _#318:https://github.com/pytest-dev/pytest-mock/pull/3188

v3.8.2

Compare Source

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

.. _#302:https://github.com/pytest-dev/pytest-mock/pull/3022

v3.8.1

Compare Source

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

.. _#298:https://github.com/pytest-dev/pytest-mock/issues/2988

v3.8.0

Compare Source

• Add MockerFixture.async_mock method. Thanks @PerchunPak_ for the PR (#296_).

.. _@​PerchunPak: https://github.com/PerchunPak
.. https://github.com/pytest-dev/pytest-mock/pull/296pull/296

v3.7.0

Compare Source

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: django-starter/Pipfile.lock

Command failed: install-tool pipenv 2025.0.2