chore(deps-dev): bump aiointercept from 0.1.7 to 0.1.8

[dependabot]

Bumps aiointercept from 0.1.7 to 0.1.8.

Changelog

Sourced from aiointercept's changelog.

[0.1.8] - 2026-06-28

Added

• m.ordered_requests — flat list of (key, AiointerceptRequest) tuples in arrival order, giving cross-URL request ordering that m.requests (grouped by key) does not provide.
• m.call_count — integer property; total requests intercepted across all URLs (len(m.ordered_requests)).
• MockResponse — object returned by m.add() / m.get() / m.post() etc. Its call_count attribute increments each time that specific registration is matched and served, enabling per-handler assertions: rsp = m.get(url); ...; assert rsp.call_count == 2.
• m.last_request — property returning the most recently intercepted AiointerceptRequest, or None if no requests have been made.
• Streaming response bodies: body= now accepts an AsyncIterable[bytes] (e.g. an async generator). aiohttp wraps it in an AsyncIterablePayload and streams the chunks with chunked transfer encoding, so the client receives each piece as it is written — useful for mocking server-sent events / OpenAI-style streaming endpoints. The iterator is drained once: with repeat only the first response carries the body and later ones come back empty, so register a fresh iterator per expected request. Related to aioresponses#274.

Fixed

• start() now clears m.requests and m.ordered_requests at the beginning of each session. Previously, reusing the same instance across multiple invocations (decorator mode or manual start()/stop() cycles) accumulated requests from prior runs, causing assert_called_once() and assert_not_called() to report stale counts. Recorded requests remain accessible after stop() for post-context-manager inspection.
• passthrough_unmatched proxying no longer truncates compressed upstream responses: the upstream Content-Length (the compressed size) was relayed alongside the already-decompressed body.
• Proxied redirects are now relayed untouched (allow_redirects=False upstream), so the client's own redirect handling (allow_redirects, response.history) behaves as it would against the real network. Previously the proxy followed redirects itself and the client saw only the final response.
• The internal proxy session no longer accumulates cookies across proxied requests (it now uses a DummyCookieJar); cookie state belongs to each test's own client.
• Custom resolvers passed to TCPConnector(resolver=...) are now intercepted too. Resolution is funneled through a single TCPConnector._resolve_host patch instead of patching ThreadedResolver.resolve / AsyncResolver.resolve, which only covered those two classes.
• Calling add() before the server is started now raises RuntimeError (was AssertionError, which disappears under python -O); a URL without a host raises ValueError.
• start() now fails with a clear RuntimeError instead of blocking the caller's event loop forever if the server thread wedges during startup.

Improved

• Sequential requests to a mocked host are faster: pooled keep-alive connections that already point at the mock server are reused instead of forcing a fresh TCP connection per request (connections pointing elsewhere are still discarded).
• Mock startup is faster: the passthrough proxy session is created lazily on first use instead of eagerly on every start().
• mock_external_urls=True now installs 3 class-level patches instead of 5 (TCPConnector._resolve_host / _get_ssl_context / _get), and passthrough hosts keep normal DNS caching (the per-lookup cache clearing is gone — interception happens before the cache).

Commits

• 168c54e prepare 0.1.8 release
• 5c36230 some small fixes (#92)
• d36722c update benchmarks
• 973ac1a Update actions/setup-python digest to ece7cb0 (#90)
• cc1668a Lock file maintenance (#87)
• 1040e3b Update actions/checkout action to v7 (#91)
• 1376600 fix default brnach on aiohttp
• 889c411 streaming requests and responses (#89)
• c905dea update workflow
• 1bed5cc ordered request and call count (#88)
• 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 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)