[cursor]

Summary

Automatic post-release bump after 0.4.2 was published to PyPI and released as v0.4.2.

Change: pyproject.toml version 0.4.2 → 0.4.3.dev0 (one line).

The branch and commit were generated by .github/workflows/publish-pypi.yml (run 34330183315); its final gh pr create step failed because this repository does not permit GitHub Actions to create pull requests, so the release automation opened the PR from the workflow's branch instead. Consider allowing Actions to create PRs (Settings → Actions → Workflow permissions) or keep relying on the release automation for this step.

Type of Change

• Refactoring (version metadata only)

Alignment Checklist

• No runtime code, invariants, or public API touched

RFC Status

• Not required

Test Plan

• CI on this PR (tests, lint, Package CI) must be green; Package CI smoke-tests that openenv.__version__ == 0.4.3.dev0 for the built wheel/sdist.

Claude Code Review

N/A

  

---

Note

Low Risk
Single-line version metadata change with no runtime or API impact.

Overview
Bumps the published package version in pyproject.toml from 0.4.2 to 0.4.3.dev0 so the repo tracks the next development cycle after the 0.4.2 PyPI/release cut.

No application code, dependencies, or APIs change—only project metadata. Installed wheels will report the new version via openenv.__version__ (loaded from distribution metadata).

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

[cursor]

Alignment Review Report

Scope: this PR changes a single line — the package version in pyproject.toml (0.4.2 → 0.4.3.dev0), a standard post-release developmental bump (PEP 440). No .py files are touched.

Automated Checks

• Lint: PASS — The CI lint job is green on this PR, and ruff check src/ tests/ passes locally (all checks passed). The local .claude/hooks/lint.sh does surface formatting drift, but exclusively in files not touched by this PR:
  • envs/** — CI never formats envs/ (CI runs ruff format src/ tests/ only), so this is pre-existing drift on main.
  • src/openenv/core/README.md and src/openenv/cli/templates/openenv_env/README.md — ruff reformatting Python code blocks embedded in Markdown; pre-existing on main.
  • usort check flags tests/envs/test_grid_world.py and tests/envs/test_julia_env.py — the known pre-existing condition documented in AGENTS.md.
• Debug code: CLEAN (for this PR) — check-debug.sh lists print/TODO items in src/, but all are pre-existing and out of scope: docstring usage examples, the intentionally-deferred serve CLI stub, and a manual test script. None are introduced by this change.

Open RFCs Context

Currently open RFCs: 000, 001, 002, 003, 005, 008 (In Review) and 010 (Draft). None govern release/versioning chores, so none are relevant to this change.

Tier 1: Fixes Required

None. The diff is a single correct version-string change with no mechanical, type, import, or security issues.

Tier 2: Alignment Discussion

Principle Conflicts

None identified. A post-release .dev0 bump is consistent with the pre-1.0 Breaking Change Policy in INVARIANTS.md/PRINCIPLES.md and does not touch any API, client/server boundary, reward, or agent-isolation surface.

RFC Conflicts

None identified.

Version consistency (verified)

• src/openenv/__init__.py resolves __version__ dynamically via _load_package_version() (from package metadata), so pyproject.toml is the single source of truth — no companion file needs updating.
• No lingering OpenEnv 0.4.2 references remain (the only 0.4.2 hits are unrelated third-party dependency versions in a notebook's pip output).

Summary

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

Clean, self-consistent version bump. All CI checks are passing.

Note: the hook findings above reflect pre-existing repository state (envs/ formatting, Markdown code-block formatting, two usort test files) and are unrelated to this version bump — flagged here only for transparency, not as blockers for this PR.

  

_{Sent by Cursor Automation: Pre-review}