Bump anyio from 4.10.0 to 4.14.2

[dependabot]

Bumps anyio from 4.10.0 to 4.14.2.

Release notes

Sourced from anyio's releases.

4.14.2

• Changed ByteReceiveStream.receive() implementations to raise a ValueError when max_bytes is not a positive integer (#1191)
• Fixed CapacityLimiter.total_tokens rejecting float("inf") when the limiter was instantiated outside of an event loop. The adapter setter checked for infinity by identity (value is math.inf), so only the exact math.inf singleton was accepted, while every backend setter (using math.isinf()) accepts any positive infinity (#1189; PR by @​greymoth-jp).
• Fixed to_process.run_sync() deadlocking when the worker function writes enough data to sys.stderr to fill the (undrained) pipe buffer. The worker process now redirects sys.stderr to os.devnull as well, matching the documented behavior
• Fixed TLSStream.wrap() matching an internationalized (unicode) host name against the peer certificate using IDNA 2003 (via the standard library) instead of IDNA 2008, which could cause the host name to be matched against the wrong certificate (#1208)
• Fixed anyio.open_process() (and run_process()) ignoring the extra_groups argument, as it mistakenly passed the value of the group argument instead (#1209)
• Fixed CapacityLimiter.acquire_nowait() and CapacityLimiter.acquire_nowait_on_behalf_of() raising trio.WouldBlock instead of anyio.WouldBlock on the trio backend when there are no tokens available (#1218)
• Fixed CapacityLimiter on the asyncio backend over-granting tokens (borrowed_tokens exceeding total_tokens and available_tokens going negative) when a non-blocking acquire was made in the window between a token being released and the notified waiter resuming. The freed token is now reserved for the woken waiter right away, so the non-blocking acquire correctly raises WouldBlock (#1170; PR by @​gaoflow)
• Fixed unnecessary CPU spin when delivering cancellation from CancelScope on asyncio under certain conditions, including improper cancel scope nesting (#1111)

4.14.1

• Fixed teardown of higher-scoped async fixtures failing on asyncio with RuntimeError: Attempted to exit cancel scope in a different task than it was entered in when an async test raise an outcome exception (e.g., pytest.skip(), pytest.xfail(), or pytest.fail()) (#1179; PR by @​EmmanuelNiyonshuti)
• Fixed CapacityLimiter.total_tokens rejecting a value of 0 when the limiter was instantiated outside of an event loop, contradicting the documented behavior of allowing 0 total tokens (#1183; PR by @​nyxst4ck)

4.14.0

• Added support for Python 3.15

• Added an asynchronous implementation of the itertools module (#998; PR by @​11kkw)

• Added the local_port parameter to connect_tcp() to allow binding to a specific local port before connecting (#1067; PR by @​nullwiz)

• Added support for custom capacity limiters in async path and file I/O functions and classes

• Added the create_task() task group method for easier asyncio migration (returns a TaskHandle) (#1098)

• Changed TaskGroup.start_soon() to return a TaskHandle

• Added an option for TaskGroup.start() to return a TaskHandle (which then contains the start value in the start_value property)

• Added the cancel() convenience method to TaskGroup as a shortcut for cancelling the task group's cancel scope

• Improved the error message when a known backend is not installed to suggest the install command (#1115; PR by @​EmmanuelNiyonshuti)

• Improved anyio.Path to preserve subclass types by returning Self in methods that return path objects (#1130; PR by @​EmmanuelNiyonshuti)

• Changed the parameter type annotation in anyio.Path.write_bytes() to accept any ReadableBuffer, thus allowing it to accept bytearray and memoryview to match pathlib.Path.write_bytes() (#1135; PR by @​SAY-5)

• Changed several type annotations to only accept callables returning coroutine-like objects instead of arbitrary awaitables:

  • TaskGroup.start_soon()
  • TaskGroup.start()
  • anyio.from_thread.run()

  This reverts an earlier change from v3.7.0 which was made in error. (#1153)

• Changed anyio.run to support callables returning arbitrary awaitables at runtime on all backends. Previously, this only worked on asyncio (#1171; PR by @​gschaffner)

• Changed several classes (and their subclasses) to have __slots__ (with __weakref__):

  • anyio.CancelScope

... (truncated)

Commits

• c384f99 Bumped up the version
• dbba29d Fixed 100% CPU spin on cancel scope misuse (#1217)
• 6bbc6c3 Fix CapacityLimiter over-granting tokens on asyncio (#1172)
• 6f82b25 Refactored TestTLSStream.test_receive_invalid_max_bytes() to be less flaky
• be24b04 Relaxed timeouts to fix test flakiness
• 8113506 Fix test flakiness caused by slow callback duration logging
• 1e988b6 Fixed CapacityLimiter raising trio.WouldBlock instead of anyio.WouldBlock (#1...
• 44713f3 Pin setup-uv to a commit sha across downstream jobs (#1213)
• f1b7301 Fixed stderr writes in a worker subprocess causing a deadlock (#1207)
• 212be93 Fix flaky test_tcp_listener_same_port using a hardcoded port (#1206)
• Additional commits viewable in compare view

[claude]

🔴 Maintainers get a failing uv run --frozen pyright pre-commit/CI job after this bump that passes on the base. anyio 4.14 narrowed TaskGroup.start_soon() to callables returning coroutines, but _spawn at src/mcp/shared/jsonrpc_dispatcher.py:686 hands it fn: Callable[..., Awaitable[Any]], so strict pyright reports reportArgumentType. Fix: give start_soon a coroutine-returning static type, e.g. type _spawn's fn as Callable[..., Coroutine[Any, Any, Any]] and make the _shielded_progress/_contained_notify wrappers (or an async def shim inside _spawn) satisfy it, so every _spawn caller still type-checks. Runtime is unaffected: all callers pass async def functions.

Extended reasoning...

This is a typecheck break, not a runtime one; the condition is anyio 4.14.2's start_soon annotation being Coroutine-returning (the PR's own release notes state the narrowing from arbitrary awaitables, reverting v3.7.0).
uv.lock:73 now pins anyio 4.14.2; pyproject.toml:159 sets typeCheckingMode = "strict" with venv = ".venv", so pyright reads anyio's annotations from the locked install.
.pre-commit-config.yaml:47 runs uv run --frozen pyright; .github/workflows/shared.yml:27-29 syncs --frozen and runs pre-commit, so CI executes this against 4.14.2.
src/mcp/shared/jsonrpc_dispatcher.py:671-686: _spawn(self, fn: Callable[..., Awaitable[Any]], *args, sender_ctx) ends with self._tg.start_soon(fn, *args) at line 686 with no # pyright: ignore.
Awaitable[Any] is not assignable to Coroutine[Any, Any, Any] (nor to any coroutine-like protocol with send/throw), so pyright emits an argument-type error there. Line 684 (sender_ctx.run(self._tg.start_soon, fn, *args)) is not flagged because Context.run takes *args: Any.
On the base, anyio 4.10 annotates the…

Verification: normal — triggered whenever the locked anyio 4.14.2 is installed (pre-commit job: .github/workflows/shared.yml:27 uv sync --frozen --all-extras then pre-commit --all-files, whose pyright hook is uv run --frozen pyright at .pre-commit-config.yaml:47) and anyio 4.14's TaskGroup.start_soon is annotated as taking a Coroutine-returning callable, which is what anyio's 4.14.0 changelog entry…