[cursor]

Release PR: v0.11.0 (rolling candidate)

Merge only with an exact-head guard (--match-head-commit) and --subject "Release OpenEnv 0.11.0 (#<this PR>)". Thursday's release run decides whether to publish.

Candidate state (Wednesday 2026-10-28 run, base main a6d28508, head 17e39e0b):

• Version lines only: pyproject.toml, envs/grid_world_env/uv.lock, tests/validation_runtime/uv.lock (0.10.1.dev0 -> 0.11.0).
• Why minor: new public features since v0.10.0 - openenv serve now runs an env locally via uvicorn (feat(cli): add openenv serve for local uvicorn #668, was a stub), new optional KubernetesProvider (Add a Kubernetes container provider #1254, openenv[kubernetes] extra; the uninstantiable placeholder export from openenv.core.containers.runtime is removed), /schema gains a reset field (Add reset schema publication to /schema endpoint #1270), volumes forwarded by LocalDockerProvider (Forward volume mounts in LocalDockerProvider #1151). Fixes: fix: cli build and push #377 CLI build/push/init, fix: expose mode-aware MCP tools via JSON-RPC #1325 mode-aware MCP JSON-RPC tools, Close persistent HTTP sessions during graceful shutdown #1447 HTTP session shutdown, Preserve task assignments when reusing CollectRunner #1467 CollectRunner, Release sync child loops after failed connections #1465, rubrics: keep Sequential awaitable when a sync child stops the chain #1473, fix(cli): package the init template Docker ignore file #1480, git_server_client: store Gitea credentials that match the server URL #1487, fix(qed): keep spawned verifier imports lightweight #1491.
• Alternative if a patch release is preferred: 0.10.1 (recommend against; new public API).

Outstanding blockers / decisions:

• Version decision 0.11.0 vs 0.10.1 (silence = 0.11.0).
• chore(deps): update fastmcp requirement from <4.0.0,>=3.0.0 to >=3.0.0,<5.0.0 #1331 (FastMCP 4) excluded: breaks session persistence, needs migration.
• Open dependabot chore(deps): bump dnspython from 2.8.0 to 2.9.0 in /tests/validation_runtime #1510 / chore(deps): bump authlib from 1.7.2 to 1.9.1 in /envs/wildfire_env #1511 are lockfile-only and not in this candidate.

Release checklist

• pyproject.toml version changed from 0.10.1.dev0 to 0.11.0
• hf-staging/ is not in the diff
• uv build succeeds
• CI gates green on the exact head
• TestPyPI validation (testpypi/0.11.0 push trigger)
• Echo reset/step smoke test
• Tag v0.11.0, publish-pypi.yml, GitHub release, fresh PyPI install verified
• Next dev bump PR (0.11.1.dev0)

Recorded state: candidate head 17e39e0b, no release lock, no Slack message sent yet.

  

---

Note

Low Risk
Version and lockfile-only changes with no runtime logic modified in this diff.

Overview
This PR only updates release metadata: it moves the package version from 0.10.1.dev0 to 0.11.0 in pyproject.toml and keeps the editable openenv entries in envs/grid_world_env/uv.lock and tests/validation_runtime/uv.lock in sync with that version.

There are no application or library code changes in the diff—just the version string and lockfile pins ahead of tagging and PyPI publish for v0.11.0.

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

[cursor]

Release state, Wednesday 2026-10-28 06:30 UTC

• Candidate head 17e39e0b on main a6d28508; diff vs main is the 3 version lines. CI 13/13 green on this head. Still draft.
• Local uv build, twine check, clean-venv wheel install (openenv 0.11.0, CLI incl. openenv serve) and a real Echo reset + call_tool step all pass.
• TestPyPI run 40641818832 (testpypi/0.11.0, 0.11.0.dev231): build job succeeded and its wheel is byte-identical to the local candidate build (203 non-metadata members, zero diffs). Publish job FAILED: invalid-publisher. The repo is now openenv/OpenEnv, but the TestPyPI trusted publisher (and, presumably, the PyPI one) is still registered for huggingface/OpenEnv.
• Blocker for Thursday: a PyPI/TestPyPI owner must add trusted publishers for repository openenv/OpenEnv (workflows publish-pypi.yml env pypi, publish-testpypi.yml env testpypi). Without it the production publish will fail; I will not tag until that is fixed.
• Decision: version 0.11.0 (new openenv serve, KubernetesProvider, /schema reset field) vs 0.10.1. Silence = 0.11.0.
• Merge only with --subject "Release OpenEnv 0.11.0 (#1514)" and --match-head-commit <head>.
• No release lock held, no subscriptions.

View PR

  

_{Sent by Cursor Automation: Release}

[cursor]

Alignment Review Report

Automated Checks

• Lint: N/A — uv isn't available in this sandbox to run ruff/usort, but it's moot regardless: the diff touches no Python source, only version strings in pyproject.toml and two uv.lock files.
• Debug code: CLEAN — check-debug.sh only flags pre-existing print() calls and TODOs in unrelated files (e.g. mcp_client.py, env_client.py, generic_client.py, harbor/*), none of which are part of this PR's 3 changed files.

Open RFCs Context

Draft/In Review RFCs currently open: 000, 001, 002, 003, 005, 006, 008, 012, 014 (In Review) and 010, 011 (Draft). None are relevant here — this PR is a pure version bump with no code, API, or architectural change.

Tier 1: Fixes Required

None. The change is exactly the expected release shape: 0.10.1.dev0 → 0.11.0 in pyproject.toml, envs/grid_world_env/uv.lock, and tests/validation_runtime/uv.lock. These are the only two uv.lock files that track openenv via an editable/path source (source = { editable = "../../" } / { directory = "../../" }); every other env's uv.lock pins a frozen published snapshot (0.3.1) and is intentionally not touched on release, matching the pattern of the prior accepted releases (0.9.0, 0.9.1, 0.10.0). No missed version references found.

Tier 2: Alignment Discussion

Principle Conflicts

None identified. No API, client/server boundary, or reward-computation code is touched.

RFC Conflicts

None identified. No area covered by an open RFC (e.g. RFC 014 Environment Services, RFC 003 MCP support) is affected by this diff.

Summary

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

This is a clean, mechanical release PR — safe to merge.

  

_{Sent by Cursor Automation: Pre-review}