chore(deps): bump anyio from 4.12.1 to 4.14.2 in /envs/carla_env

[dependabot]

Bumps anyio from 4.12.1 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

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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

Note

Low Risk
Lockfile-only transitive dependency bump with no repo code changes; typical low blast radius, though async networking/test behavior may shift slightly via upstream fixes.

Overview
Updates the carla_env uv.lock to pin anyio from 4.12.1 to 4.14.2 (sdist and wheel URLs/hashes only). There are no application or dependency manifest edits in this PR—only the locked transitive async I/O library version changes for that environment.

The newer release is mostly bug fixes (capacity limiters, TLS host matching, subprocess/stderr deadlocks, cancel-scope behavior) plus minor API additions; anything in carla_env that pulls anyio through stacks like httpx / gradio will resolve to the updated build on the next install.

^{Reviewed by Cursor Bugbot for commit 11a12ad. Bugbot is set up for automated code reviews on this repo. Configure here.}

[bot-ci-comment]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[cursor]

Alignment Review Report

Automated two-tier review of this Dependabot lockfile bump — anyio 4.12.1 → 4.14.2 in envs/carla_env (single file, +3/−3).

Automated Checks

• Lint: PASS (N/A to this diff). The change is uv.lock-only; ruff/usort only cover src/+tests/, and .lock/TOML aren't linted at all. CI lint is green. (The local .claude/hooks/lint.sh couldn't execute in this review sandbox because uv isn't preinstalled — unrelated to this PR.)
• Debug code: CLEAN. check-debug.sh scans src/ only; every hit is pre-existing and none are in the changed lockfile.

Open RFCs Context

Open RFCs (000/001/002/003/005/008 In Review; 010/011 Draft) cover abstractions, env-spec, MCP, agentic harnesses, environment auto-validation, and token world-modeling. None govern dependency management / PyPI resolution, so a transitive lockfile bump has no RFC surface.

Tier 1: Fixes Required

None. Verification performed:

• Hashes authentic (match PyPI exactly): wheel sha256:9f50…1494 (125,813 B) and sdist sha256:cfa1…c7f (260,176 B); yanked: false.
• Transitive dep — anyio is not pinned anywhere in carla_env (it arrives via fastapi/starlette/httpx/openai/mcp), so a lock-only edit is the correct shape.
• Constraints satisfied — carla_env requires-python >=3.11 ⊆ anyio >=3.10; anyio's runtime deps (idna, typing_extensions; py<3.13) are already locked. (No sniffio needed: anyio dropped that runtime dep — the sniffio in this lock belongs to openai.)
• Minimal & consistent — only the version/sdist/wheel lines changed; no other artifact lines touched, revision stays 3, and the lock is already 100% pypi.org/simple (0 mirror refs, before and after). So no index-flip and no revision-bump side-effects this time.
• CI validate-env-locks, Build and smoke-test package, docs build, snapshot, and thinkingbox tests are all green; only the main test (3.11/3.12) matrix is still pending (an anyio minor bump is low-risk for it).

Tier 2: Alignment Discussion

Principle Conflicts

None identified — no change to the Gymnasium API, client/server boundary, reward computation, or MCP surface.

RFC Conflicts

None identified.

Process observation (non-blocking)

ALIGNMENT FLAG: Dependabot exclude-paths bypass

• Config at stake: .github/dependabot.yml — the uv updater declares directory: "/" with exclude-paths: ["envs/**"].
• The concern: this native dependabot/uv/envs/carla_env/… PR edits envs/carla_env/uv.lock despite that exclusion. exclude-paths is a valid key, but the uv ecosystem doesn't appear to honor it (recurring across prior native env bumps). Not a defect in this PR — worth confirming whether env locks are intended to flow through the aggregate roll-up path instead.
• Suggested reviewer: @burtenshaw (authored the exclude-paths config).

Summary

• 0 mechanical issues to fix
• 0 principle/RFC conflicts
• 1 non-blocking process observation (Dependabot exclude-paths bypass)

Net-positive security bump. 4.12.1 is affected by two advisories, both fixed in exactly 4.14.2:

• GHSA-82r6-8w77-94w6 / CVE-2026-63374 — IDNA-2003 TLS certificate-validation confusion in connect_tcp() / TLSStream.wrap().
• GHSA-5p39-cfhj-2xmp / CVE-2026-64847 — process-pool worker stderr pipe never drained → DoS wedge.

Recommend merge once the test matrix goes green.

  

_{Sent by Cursor Automation: Pre-review}

[cursor]

Verified against PyPI: anyio 4.14.2 wheel sha256:9f50…1494 (125,813 B) and sdist sha256:cfa1…c7f (260,176 B) match exactly; yanked: false.

This is a security bump — 4.12.1 is affected by CVE-2026-63374 (IDNA-2003 TLS cert-validation confusion) and CVE-2026-64847 (process-pool stderr DoS), both fixed in 4.14.2.

Transitive dep (idna + typing_extensions; py<3.13 already locked; anyio no longer requires sniffio). Minimal, born-clean bump: no index-flip, revision unchanged (3).

[cursor]

Superseded: anyio 4.14.2 for this env landed via the batched merge in #1202 (39fdf5cd). Please close this PR (this automation cannot close PRs).

View PR

  

_{Sent by Cursor Automation: Release}

[dependabot]

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.