Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency pook to v2 #406

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 1, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pook 1.4.3 -> 2.1.3 age adoption passing confidence

Release Notes

h2non/pook (pook)

v2.1.3

Compare Source

  • Ensure aiohttp headers can be matched from both the session and request in the same matcher

v2.1.2

Compare Source

v2.1.1

Compare Source

v2.1.0

Compare Source

  • Drop support for Python 3.8 (it is EOL 2024-10-07)

v2.0.1

Compare Source

v2.0.0

Compare Source

See https://github.com/h2non/pook/issues/128 for a summary of the breaking changes and how to update your code if you are affected.

  • Breaking change: Remove Response::body's binary parameter and enforce a keyword argument for chunked.

    • The binary parameter is no longer needed since responses are now always byte-encoded in all cases (see below).
    • A keyword argument is now enforced for chunked to ensure unnamed arguments meant for the removed binary parameter cannot be confused as chunked arguments.
  • Only return byte-encoded response bodies, matching the bahviour of all supported client libraries.

    • This is possible because for all supported client libraries, pook mocks the actual response sent to the
      client library over the wire, which will, in all cases, be bytes. Client libraries that support reading
      response content as a string or other formats will continue to work as expected, because they'll always
      be handling bytes from pook.
    • This causes no change to application code for users of pook, except for users of the standard library urllib,
      for which this also fixed a bug where non-bytes bodies were returned by pook in certain cases. This is impossible
      in real application code. If you rely on pook to mock urllib responses and have code that handles non-bytes response
      bodies, that code can be safely deleted (provided the only reason it was there was pook in the first place).
  • Breaking change: Remove Mock::body's binary parameter.

    • This parameter was already unused due to a bug in the code (it was not passed through to the BodyMatcher),
      so this will not cause any changes to tests that relied on it: it didn't do anything to begin with.
    • The breaking change is simply the removal of the unused parameter, which should be deleted from tests using pook.
    • Pook's code has also been updated to remove all cases where non-bytes objects were being handled. Instead, the body
      of any interecepted request will always be stored as bytes, and only decoded when necessary for individual downstream
      matchers (JSON, XML).
  • Correct documentation strings for XMLMatcher and JSONMatcher to no longer suggest they can handle regex matchers.

    • These classes never implemented regex matching.
  • Add a pytest fixture to the package.


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 is behind base branch, 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.

Copy link

github-actions bot commented Jul 1, 2024

Coverage report

This PR does not seem to contain any modification to coverable code.

@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 2 times, most recently from 11ac9fa to e54d68d Compare July 8, 2024 01:38
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 3 times, most recently from ba165f2 to a22d000 Compare July 15, 2024 01:02
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 3 times, most recently from d557a85 to e57eab4 Compare July 25, 2024 17:35
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 4 times, most recently from 086b281 to abf1ea6 Compare August 5, 2024 02:00
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 8 times, most recently from 23bf582 to 171bfb8 Compare August 12, 2024 01:18
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 2 times, most recently from f7faac7 to e5c3f8f Compare August 19, 2024 01:39
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 3 times, most recently from 80ff237 to 2cccac5 Compare September 2, 2024 00:42
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch from 2cccac5 to 012a62f Compare October 8, 2024 04:43
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 3 times, most recently from 1583d23 to a1d0364 Compare October 24, 2024 09:38
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 7 times, most recently from ca01de3 to fe1b8ae Compare October 29, 2024 22:14
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 3 times, most recently from 851225f to d5830a9 Compare November 11, 2024 01:17
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 2 times, most recently from 9f10950 to 5875efb Compare November 25, 2024 00:50
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 4 times, most recently from 8326dfc to 5a0fe7d Compare December 6, 2024 23:26
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch 2 times, most recently from 7ed5408 to a5f6489 Compare December 16, 2024 00:18
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch from a5f6489 to fd5ceab Compare December 21, 2024 23:03
@renovate renovate bot force-pushed the renovate/pook-2.x-lockfile branch from fd5ceab to baf81c8 Compare December 23, 2024 01:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants