chore(deps): bump anyio from 4.12.1 to 4.14.2 in /envs/grid_world_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 dependency resolution; behavior changes would come from upgraded transitive libraries (notably anyio), not from env code edits.

Overview
Updates envs/grid_world_env/uv.lock so resolved dependencies match the current tree, not just a single package pin.

anyio is bumped from 4.12.1 to 4.14.2 (async I/O / pytest-asyncio transitive dependency). That release line includes bug fixes around cancel scopes, capacity limiters, TLS host matching, and subprocess stderr deadlocks.

The lockfile also picks up the editable openenv bump (0.4.2.dev0 → 0.5.1.dev0): adds packaging, caps fastmcp to <4.0.0, expands optional extras (novita, harbor), and adds jsonschema under dev metadata. secretstorage’s dependency entries lose platform markers on cryptography / jeepney as part of the same resolve.

No application source under grid_world_env changes—only the lockfile.

^{Reviewed by Cursor Bugbot for commit a6f9d0d. 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

Scope: envs/grid_world_env/uv.lock only (1 file, +13/−8). Lockfile-only change — no Python/source files touched.

Automated Checks

• Lint: FAIL at repo level, but not attributable to this PR. ruff format --check src/ tests/ envs/ flags 56 pre-existing files and usort check src/ tests/ flags 2 (tests/envs/test_julia_env.py, tests/envs/test_grid_world.py — both documented as pre-existing in AGENTS.md). None are in grid_world_env, and this PR changes no .py files, so it introduces zero lint regressions.
• Debug code: FOUND at repo level, but not attributable to this PR. The hook found many print/TODO occurrences, all under src/openenv/** (the hook only scans src/). This PR's diff is a lockfile, so none of the findings come from it.
• Lockfile validity: PASS. uv lock --check in envs/grid_world_env succeeds (resolved 117 packages) — the lock is internally consistent and up-to-date with pyproject.toml.

Open RFCs Context

All RFCs are currently In Review or Draft (none Accepted/Implemented):

• Draft: 010 (ECHO token world model), 011 (ARD catalog discovery)
• In Review: 000, 001, 002, 003, 005, 008, 012 (Harbor capture providers) — 004 (Rubrics) uses a non-standard status header.

Only RFC 012 (Harbor) touches an area that surfaces in this diff (the harbor extra now appears in the lock). This is not a conflict: the harbor/novita extras were already added to the root openenv package in prior merged PRs (e.g. #1191 NovitaSandboxProvider); this lock is merely catching up. No design decision is made in this PR.

Tier 1: Fixes Required

• None. This PR touches only uv.lock, the lock passes uv lock --check, and it introduces no lint or debug regressions.

Tier 2: Alignment Discussion

Principle Conflicts

None identified. A lockfile bump makes no API, client/server-separation, reward-boundary, or MCP changes; no PRINCIPLES.md or INVARIANTS.md item is affected.

RFC Conflicts

None identified. (RFC 012 noted above for context only — the harbor entries are downstream of already-merged root changes.)

Note on scope (informational, not a blocker)

Though the title says "bump anyio 4.12.1 → 4.14.2", regenerating the lock also pulled in drift that had accumulated in the root openenv package since this env's lock was last updated. Every extra entry was verified against the current root pyproject.toml:

• openenv 0.4.2.dev0 → 0.5.1.dev0 (post-release version bump)
• + packaging>=24.2 (now a core dependency)
• fastmcp >=3.0.0 → >=3.0.0,<4.0.0
• + novita extra (novita-sandbox>=2.1.1) and + harbor extra
• + jsonschema>=4.20.0 (dev group)
• secretstorage transitive markers simplified by the resolver

These faithfully reflect already-merged root changes rather than new decisions here, so the broad diff is expected dependabot behavior.

Summary

• 0 mechanical issues to fix
• 0 alignment points for human review
• 0 RFC conflicts to discuss

No alignment concerns. Recommend letting the normal CI (tests) gate confirm runtime compatibility of anyio 4.14.2.

  

_{Sent by Cursor Automation: Pre-review}

[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.