search

anaynayak / buildnotify

A system tray based build status notification app for cctray.xml feeds.
https://anaynayak.github.io/buildnotify/
Other
29 stars 7 forks source link

Bump pytest-mock from 3.7.0 to 3.8.2 #255

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps pytest-mock from 3.7.0 to 3.8.2.

Release notes

Sourced from pytest-mock's releases.

v3.8.2

3.8.2 (2022-07-05)

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

v3.8.1

Releases

3.8.1 (2022-06-24)

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

3.8.0 (2022-06-24)

3.7.0 (2022-01-28)

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

3.6.1 (2021-05-06)

3.6.0 (2021-04-24)

  • pytest-mock no longer supports Python 3.5.
  • Correct type annotations for mocker.patch.object to also include the string form. Thanks @​plannigan for the PR (#235).
  • reset_all now supports return_value and side_effect keyword arguments. Thanks @​alex-marty for the PR (#214).

3.5.1 (2021-01-10)

  • Use inspect.getattr_static instead of resorting to object.__getattribute__ magic. This should better comply with objects which implement a custom descriptor protocol. Thanks @​yesthesoup for the PR (#224).

3.5.0 (2021-01-04)

  • Now all patch functions will emit a warning instead of raising a ValueError when used

... (truncated)

Changelog

Sourced from pytest-mock's changelog.

3.8.2 (2022-07-05)

  • Fixed AsyncMock support for Python 3.7+ in mocker.async_stub ([#302](https://github.com/pytest-dev/pytest-mock/issues/302)_).

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

3.8.1 (2022-06-24)

  • Fixed regression caused by an explicit mock dependency in the code ([#298](https://github.com/pytest-dev/pytest-mock/issues/298)_).

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

3.8.0 (2022-06-24)

  • Add MockerFixture.async_mock method. Thanks @PerchunPak_ for the PR ([#296](https://github.com/pytest-dev/pytest-mock/issues/296)_).

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

Commits


Dependabot compatibility score

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 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[bot] commented 2 years ago

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[bot] commented 2 years ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.