chore: bump version to 0.6.1.dev0 (post-release) - #1245
Conversation
Co-authored-by: benjamin.burtenshaw <benjamin.burtenshaw@huggingface.co>
There was a problem hiding this comment.
Alignment Review Report
Automated Checks
- Lint: N/A — this review sandbox has no
uv/ruff/usorttoolchain, so.claude/hooks/lint.shcould not execute. It is also inapplicable here: the diff changes 0 Python files (onlypyproject.toml+ twouv.lockfiles), and the lint hook only targets.pyfiles undersrc//tests/. - Debug code: CLEAN for this PR.
check-debug.shscans the wholesrc/tree and surfaced many pre-existingprint/TODOlines (harbor, CLI commands, docstring examples), but none are introduced by this diff. This change adds no debug code.
Open RFCs Context
Open RFCs at review time — In Review: 000 (project phases), 001 (abstractions), 002 (env spec), 003 (MCP support), 005 (agentic harnesses), 008 (env auto-validation), 012 (harbor capture providers); Draft: 010 (echo-env token world model), 011 (ARD catalog discovery). (004 rubrics has no explicit status line.) None concern version numbering or release mechanics, so none are relevant to this change.
Tier 1: Fixes Required
None. This is a mechanical post-release version bump 0.6.0 → 0.6.1.dev0:
pyproject.toml—[project].versionbumpedenvs/grid_world_env/uv.lock—openenveditable entry syncedtests/validation_runtime/uv.lock—openenvdirectory entry synced
Completeness/consistency verified:
- These are the only two lockfiles that pin
openenvfrom the local repo (editable/directory = "../../"); both were correctly synced. The other 37 env lockfiles referenceopenenvfrom external sources (PyPI, HF registry, or pinned git SHAs) at 0.3.x/0.4.x and are correctly left untouched. - No stray hardcoded
0.6.0remains elsewhere (the only non-lock match is an unrelatedannotated-types>=0.6.0line in a notebook).src/openenv/__init__.pyderives__version__dynamically from package metadata, so no code change is needed. 0.6.0 → 0.6.1.dev0is a pre-1.0 patch-level dev bump, consistent with the Breaking Change Policy inINVARIANTS.md.
Tier 2: Alignment Discussion
Principle Conflicts
None identified. The change touches no API signatures, client/server boundaries, reward logic, or MCP/WebSocket interfaces — it only updates version strings and their lockfile reflections.
RFC Conflicts
None identified. No open RFC covers version/release mechanics.
Summary
- 0 mechanical issues to fix
- 0 alignment points for human review
- 0 RFC conflicts to discuss
Note: lint.sh/check-debug.sh were not fully executable in this review sandbox (no uv toolchain), but neither applies to this diff since it contains no Python source changes.
Sent by Cursor Automation: Pre-review


Post-release development bump after
openenv==0.6.0was published to PyPI.pyproject.toml:0.6.0→0.6.1.dev0(reuses the commitpublish-pypi.ymlpushed tobump/0.6.1.dev0; its own PR-creation step is not permitted for GitHub Actions)openenventries inenvs/grid_world_env/uv.lockandtests/validation_runtime/uv.locksynced to match, as in Release OpenEnv 0.6.0 #1211.uv lock --checkpasses for both.No code changes. Release: https://github.com/huggingface/OpenEnv/releases/tag/v0.6.0
Note
Low Risk
Version and lockfile metadata only; no runtime or behavioral changes.
Overview
Bumps the openenv package version from
0.6.0to0.6.1.dev0inpyproject.tomlso the repo reflects the next development cycle after the0.6.0PyPI release.The editable
openenventries inenvs/grid_world_env/uv.lockandtests/validation_runtime/uv.lockare updated to the same version so those lockfiles stay in sync with the root project. No application or library code changes.Reviewed by Cursor Bugbot for commit a8042d3. Bugbot is set up for automated code reviews on this repo. Configure here.