[cursor]

Automatic post-release bump after 0.5.0 was published.

Change: pyproject.toml version 0.5.0 → 0.5.1.dev0

Opened by the release automation because .github/workflows/publish-pypi.yml could not create the PR (GitHub Actions is not permitted to create pull requests).

  

---

Note

Low Risk
Single metadata version field change with no code or dependency impact.

Overview
Bumps the openenv package version in pyproject.toml from 0.5.0 to 0.5.1.dev0 as the standard post-release dev identifier after 0.5.0 was published to PyPI.

No runtime, API, or dependency changes—only the declared project version for the next development cycle.

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

[cursor]

Alignment Review Report

chore: bump version to 0.5.1.dev0 (post-release) — a single-line change to pyproject.toml (0.5.0 → 0.5.1.dev0). No .py, workflow, or docs files are touched.

Automated Checks

• Lint: PASS (for this PR's scope). .claude/hooks/lint.sh exits non-zero, but every failure is pre-existing drift unrelated to this PR: ~26 envs/** files flagged by ruff format --check, plus the two long-standing usort files tests/envs/test_grid_world.py and tests/envs/test_julia_env.py (documented in AGENTS.md). This PR edits only pyproject.toml, which ruff/usort do not lint, and ruff check src/ tests/ is clean.
• Debug code: CLEAN. check-debug.sh lists only pre-existing print/console.print under src/; this PR changes no .py.

Open RFCs Context

Open RFCs: 000–003, 005, 008, 012 (In Review); 004 (no status header; rewards/rubrics); 010–011 (Draft). None govern package versioning or release mechanics, so none are affected by this change.

Tier 1: Fixes Required

None. The bump is correct and complete:

• Valid PEP 440 pre-release; orders correctly (0.5.0 < 0.5.1.dev0 < 0.5.1).
• Single source of truth — src/openenv/__init__.py derives __version__ dynamically via importlib.metadata, so there is no second hardcoded string to update.
• uv.lock is git-ignored (not committed), so there is no lockfile version to drift.
• Matches the established post-release convention (last cycle: 0.4.2 → 0.4.3.dev0 in #1133).

Tier 2: Alignment Discussion

Principle Conflicts: None identified. A version bump touches none of the design surfaces (Gymnasium API, rewards-in-environment, client-server separation, MCP boundary, container isolation).

RFC Conflicts: None identified.

Summary

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

Routine, safe post-release bump. publish-pypi.yml triggers only on v*.*.* tags, so merging .dev0 to main will not publish to PyPI. FYI @burtenshaw as packaging/release owner — no action needed.

  

_{Sent by Cursor Automation: Pre-review}

[cursor]

Correct post-release bump. 0.5.1.dev0 is valid PEP 440 and sorts between the tagged 0.5.0 and the eventual 0.5.1 (0.5.0 < 0.5.1.dev0 < 0.5.1), so main is now clearly marked as in-development ahead of the v0.5.0 release.

Nothing else needs to change alongside it: __version__ is resolved dynamically from distribution metadata in src/openenv/__init__.py (no second string to sync), uv.lock is git-ignored, and publish-pypi.yml only publishes on v*.*.* tags.