chore(deps): update dependency pytest-mock to v3.17.0 #122

Open
renovate wants to merge 1 commit from renovate/dev-dependencies into main
Collaborator

This PR contains the following updates:

Package Change Age Confidence
pytest-mock (changelog) ==3.16.1 → ==3.17.0 age confidence

Release Notes

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

v3.17.0

Compare Source

2026-10-17

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

Configuration

📅 Schedule: (UTC)

  • 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 has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [pytest-mock](https://github.com/pytest-dev/pytest-mock) ([changelog](https://pytest-mock.readthedocs.io/en/latest/changelog.html)) | `==3.16.1` → `==3.17.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest-mock/3.17.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest-mock/3.16.1/3.17.0?slim=true) | --- ### Release Notes <details> <summary>pytest-dev/pytest-mock (pytest-mock)</summary> ### [`v3.17.0`](https://github.com/pytest-dev/pytest-mock/blob/HEAD/CHANGELOG.rst#3170) [Compare Source](https://github.com/pytest-dev/pytest-mock/compare/v3.16.1...v3.17.0) *2026-10-17* - `#&#8203;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. - `#&#8203;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. - `#&#8203;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. </details> --- ### Configuration 📅 **Schedule**: (UTC) - 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNzguNSIsInVwZGF0ZWRJblZlciI6IjQ0LjE5MC4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
chore(deps): update dependency pytest-mock to v3.17.0
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
ci/woodpecker/pr/check-code/1 Pipeline was successful
ci/woodpecker/pr/check-commits Pipeline was successful
ci/woodpecker/pr/check-code/2 Pipeline was successful
ci/woodpecker/pr/checks Pipeline was successful
8b6fc2b345
renovate force-pushed renovate/dev-dependencies from 8b6fc2b345
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
ci/woodpecker/pr/check-code/1 Pipeline was successful
ci/woodpecker/pr/check-commits Pipeline was successful
ci/woodpecker/pr/check-code/2 Pipeline was successful
ci/woodpecker/pr/checks Pipeline was successful
to da885a5361
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
ci/woodpecker/pr/check-commits Pipeline was successful
ci/woodpecker/pr/check-code/1 Pipeline was successful
ci/woodpecker/pr/check-code/2 Pipeline was successful
ci/woodpecker/pr/checks Pipeline was successful
2026-10-30 07:16:08 +00:00
Compare
renovate force-pushed renovate/dev-dependencies from da885a5361
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
ci/woodpecker/pr/check-commits Pipeline was successful
ci/woodpecker/pr/check-code/1 Pipeline was successful
ci/woodpecker/pr/check-code/2 Pipeline was successful
ci/woodpecker/pr/checks Pipeline was successful
to 69f2fe7150
Some checks failed
renovate/stability-days Updates have met minimum release age requirement
ci/woodpecker/pr/check-code/1 Pipeline was successful
ci/woodpecker/pr/check-commits Pipeline was successful
ci/woodpecker/pr/check-code/2 Pipeline failed
ci/woodpecker/pr/checks Pipeline was skipped
2026-10-30 09:15:46 +00:00
Compare
Some checks failed
renovate/stability-days Updates have met minimum release age requirement
ci/woodpecker/pr/check-code/1 Pipeline was successful
ci/woodpecker/pr/check-commits Pipeline was successful
ci/woodpecker/pr/check-code/2 Pipeline failed
ci/woodpecker/pr/checks Pipeline was skipped
Required
Details
Some required checks were not successful.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/dev-dependencies:renovate/dev-dependencies
git switch renovate/dev-dependencies
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
BjoernPetersen/bs-lock!122
No description provided.