Repository navigation
Release OpenEnv 0.12.1 - #1577
Conversation
Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
There was a problem hiding this comment.
Release state, Wednesday 2026-11-11 (supersedes the PR title/body, which still say 0.12.1; I cannot edit them with the current token).
- Candidate version: 0.13.0 (minor). Since v0.12.0, main added the
openenv importAgentEnv importer (#1493), session telemetry (#1320), RFC 008 runtime validation graders (containment, discovery, isolation, oracle, repeatability, resources),openenv harbor export-sft, and Modal sandbox v2 changes. INVARIANTS.md treats new public features as MINOR. - Head
d8a82dcf= main029c08f8plus 3 version lines (pyproject.toml, envs/grid_world_env/uv.lock, tests/validation_runtime/uv.lock). Diff vs main is the version bump only. - CI on exact head: all checks green (tests 3.11/3.12, lint, package smoke, runtime validation Docker, env locks, CodeQL, ortools/tau2/thinkingbox).
buildskipped. - Local:
uv build+twine checkpass; clean-venv wheel install,openenv --help, and a real Echo reset/list_tools/step pass. - TestPyPI
0.13.0.dev281(run 42969584289, scratch branchtestpypi/0.13.0): wheel is byte-identical to the local build (221 non-dist-info members). - Excluded: fork PRs without CI (#1576 #1572 #1570 #1569 #1561 #1571 and others), #1573 (feature), #1331 (fastmcp 4), dependabot PRs #1583-#1588 (not release-relevant).
- Stage: candidate validated. No lock, no tag, nothing published. Thursday: take
refs/release-lock/v0.13.0, re-check main vs029c08f8, merge with--subject "Release OpenEnv 0.13.0 (#1577)"and an exact-head guard, tag, publish, verify, dev bump to 0.13.1.dev0.
Sent by Cursor Automation: Release
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit d8a82dc. Configure here.
| [project] | ||
| name = "openenv" | ||
| version = "0.12.1.dev0" | ||
| version = "0.13.0" |
There was a problem hiding this comment.
Wrong version bump for release
High Severity
The version is set to 0.13.0 in pyproject.toml and the related lockfiles, but this PR is the 0.12.1 patch release. Publishing this would skip 0.12.1, consume 0.13.0 on PyPI, and fail the v0.12.1 tag check in publish-pypi.yml.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit d8a82dc. Configure here.
There was a problem hiding this comment.
Alignment Review Report
Automated Checks
- Lint: FAIL (pre-existing, not caused by this diff) —
.claude/hooks/lint.shreports 47 files repo-wide needingruff format/usortfixes. None of the three files this PR touches (pyproject.toml,envs/grid_world_env/uv.lock,tests/validation_runtime/uv.lock) are.pyfiles or part of that list, so this PR introduces zero new lint failures. - Debug code: FOUND (pre-existing, not caused by this diff) —
check-debug.shfindsprint()calls andTODOmarkers undersrc/(e.g.src/openenv/core/mcp_client.py,src/openenv/core/containers/test_local_docker_provider.py). All predate this PR; this diff adds no new debug code.
Open RFCs Context
All 12 RFCs (000–014) are currently Draft or In Review, none Accepted/Implemented. None are relevant here: this PR is a pure version bump touching only pyproject.toml and two uv.lock files, with no code, API, or behavior change, so it doesn't intersect any RFC's subject area.
Tier 1: Fixes Required
-
pyproject.toml:7, PR title/description — The PR title ("Release OpenEnv 0.12.1") and body ("patch... go from 0.12.1.dev0 to 0.12.1", "Release lock ref: refs/release-lock/v0.12.1") describe a patch release to0.12.1, but the actual diff bumps the version to0.13.0(a minor bump) in all three files. The bot's own PR summary already flags this ("The PR title still references 0.12.1, but the changes ship 0.13.0"). The PR body explicitly says it is "Awaiting human confirmation only if someone wants 0.13.0" — that confirmation isn't visible in the PR thread. Please reconcile title/description with the shipped version (or confirm 0.13.0 was intended) before merge. For context, this matches the repo's historical pattern: every prior release has bumped minor rather than the patch implied by the post-releasedev0marker (e.g.0.11.1.dev0→Release OpenEnv 0.12.0,0.12.1.dev0→ this PR's0.13.0), so the version number itself is plausible — it's the title/body wording that needs updating to match.
No other mechanical issues identified; this is a 3-line, version-string-only diff.
Tier 2: Alignment Discussion
Principle Conflicts
None identified. No Gymnasium API, client/server boundary, MCP/reset-exposure, or reward-computation code is touched.
RFC Conflicts
None identified. No RFC's subject area (abstractions, env spec, MCP, rubrics, harnesses, auto-validation, catalog discovery, harbor providers, environment services) overlaps a version-string-only change.
Summary
- 1 mechanical issue to fix (title/description vs. shipped version mismatch — easy to resolve, not a code defect)
- 0 alignment points for human review
- 0 RFC conflicts to discuss
Overall: safe, low-risk, metadata-only release PR. The only actionable item is reconciling the PR title/body with the 0.13.0 version actually being shipped.
Sent by Cursor Automation: Pre-review
| [project] | ||
| name = "openenv" | ||
| version = "0.12.1.dev0" | ||
| version = "0.13.0" |
There was a problem hiding this comment.
This bumps the version to 0.13.0, but the PR title/description say this is a patch release to 0.12.1. Please update the title/description to match (or confirm the minor bump to 0.13.0 was intentional) before merging — see the top-level review for details.




Summary
Rolling release PR for OpenEnv 0.12.1 (patch). Version-only change:
pyproject.toml,envs/grid_world_env/uv.lock,tests/validation_runtime/uv.lockgo from0.12.1.dev0to0.12.1. Merge with--subject "Release OpenEnv 0.12.1 (#<this PR>)".Type of Change
Candidate contents since v0.12.0 (main dbdcde2 at time of writing)
envs/, human-merged; kept out of Spaces releases)Version decision
Patch: bug fixes plus a new environment; no public core API change. Awaiting human confirmation only if someone wants 0.13.0.
Outstanding / blockers (as of Monday 2026-11-09)
--harness, feature with failing test (3.11)) excluded.Release state
RFC Status
Test Plan
CI on exact head; local build + twine check + clean-venv install + Echo reset/step smoke; TestPyPI dry run on Wednesday.
Claude Code Review
N/A
Note
Low Risk
Version and lockfile metadata only; no application logic changes in this diff.
Overview
This PR bumps the published
openenvversion from0.12.1.dev0to0.13.0in the rootpyproject.tomland keeps workspace lockfiles in sync by updating the editableopenenventry to 0.13.0 inenvs/grid_world_env/uv.lockandtests/validation_runtime/uv.lock.There are no runtime or library code changes in the diff itself—it is a release/version pin update so installs and CI environments resolve the new package version. (The PR title still references 0.12.1, but the changes ship 0.13.0.)
Reviewed by Cursor Bugbot for commit d8a82dc. Bugbot is set up for automated code reviews on this repo. Configure here.