Skip to content

chore: bump version to 0.13.1.dev0 after 0.13.0 release - #1604

Merged
cursor[bot] merged 1 commit into
mainfrom
cursor/openenv-release-process-e0a5
Nov 12, 2026
Merged

cursor[bot] merged 1 commit into
mainfrom
cursor/openenv-release-process-e0a5

Conversation

@cursor

@cursor cursor Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Post-release development bump after v0.13.0 (release PR #1577).

Changes only the version line in pyproject.toml, envs/grid_world_env/uv.lock and tests/validation_runtime/uv.lock to 0.13.1.dev0. uv lock --check passes in both lock directories.

Opened by hand because the Open post-release bump PR job in publish-pypi.yml fails again on the Actions PR-creation policy.

Open in Web View Automation 

Note

Low Risk
Version and lockfile metadata only; no runtime or dependency graph changes beyond reflecting the new dev version.

Overview
Bumps the openenv package version from 0.13.0 to 0.13.1.dev0 for post-release development after the v0.13.0 PyPI release.

The change updates pyproject.toml and the embedded openenv package entries in envs/grid_world_env/uv.lock and tests/validation_runtime/uv.lock so those editable-path locks stay in sync with the project version.

Reviewed by Cursor Bugbot for commit 73bb4fe. Bugbot is set up for automated code reviews on this repo. Configure here.

Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
@cursor
cursor Bot marked this pull request as ready for review November 12, 2026 07:02
@cursor
cursor Bot merged commit 5b2da64 into main Nov 12, 2026
15 checks passed
@burtenshaw burtenshaw added enhancement New feature or request size: small Small pull request labels Nov 12, 2026 — with Cursor

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alignment Review Report

Automated Checks

  • Lint: PASS (relative to this diff) — the only changed files are pyproject.toml and two uv.lock files; neither TOML nor lockfiles are linted by .claude/hooks/lint.sh or CI's lint job (both scope to src/, tests/, envs/**/*.py). I installed uv fresh and ran the hook anyway: it reports pre-existing ruff format/usort drift across ~47 unrelated files (various envs/** READMEs, src/openenv/core/harness/README.md, etc.) — none of them are in this PR's diff, so this is baseline noise, not something this PR introduced. gh pr checks 1604 also shows the real CI lint job green.
  • Debug code: CLEAN — check-debug.sh only scans src/, which this PR doesn't touch at all.

Open RFCs Context

Scanned all 12 RFCs (000–014, mix of Draft/In Review). None of them cover packaging, versioning, or the PyPI release process — this is a long-standing, re-confirmed gap (consistent with every prior version-bump PR reviewed under this automation). No RFC is relevant here.

Tier 1: Fixes Required

None. This is a pure 3-line mechanical version bump:

  • pyproject.toml:7 — version = "0.13.0" → "0.13.1.dev0"
  • envs/grid_world_env/uv.lock and tests/validation_runtime/uv.lock — the cached openenv entry version bumped to match, since these are the only two lockfiles that reference the root package via a local editable/directory source (every other env's uv.lock pins openenv from pypi.org at an independent released version, e.g. 0.3.1, and is unaffected by this bump).

Verified:

  • uv lock --check passes in both envs/grid_world_env and tests/validation_runtime — the lockfiles are internally consistent with the new pyproject.toml version.
  • No stale 0.13.0/stale pre-bump references remain outside the two lockfiles (rg over the repo, excluding *.lock).
  • src/openenv/__init__.py derives __version__ from installed package metadata (_load_package_version()), so there's no second hardcoded version string to keep in sync.
  • PEP 440 ordering is correct: 0.13.0 < 0.13.1.dev0 < 0.13.1.
  • publish-pypi.yml only triggers on push: tags: v*.*.*, so merging this .dev0 bump to main publishes nothing — this just marks main as in-development ahead of the v0.13.0 tag, matching the established post-release convention (e.g. #1195, #1418).
  • validate-env-locks (which gates on changed envs/*/pyproject.toml|uv.lock paths) is green per gh pr checks, and all other CI checks (lint, test ×2, package build/smoke-test, Docker runtime validation, check-env-docs, snapshot) pass.
  • Working tree is clean; no uncommitted drift from this diff.

Tier 2: Alignment Discussion

Principle Conflicts

None identified. No Gym-style API signature, reward computation, client/server import boundary, or MCP/WebSocket surface is touched.

RFC Conflicts

None identified. Versioning/packaging/release process is outside the scope of every current RFC.

Summary

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

Clean, well-formed post-release version bump. No action needed beyond the normal merge.

Open in Web View Automation 

Sent by Cursor Automation: Pre-review

Comment thread pyproject.toml
[project]
name = "openenv"
version = "0.13.0"
version = "0.13.1.dev0"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct post-0.13.0-release bump to 0.13.1.dev0 (next-patch dev marker, not next-minor) — matches the established convention from prior release cycles. uv lock --check confirms the two local-source lockfiles (envs/grid_world_env/uv.lock, tests/validation_runtime/uv.lock) are in sync with this version.

burtenshaw added a commit that referenced this pull request Nov 12, 2026
Takes the post-release version bump from #1604 (5b2da64). tests/validation_runtime/uv.lock merges cleanly: main changes only the openenv package version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request size: small Small pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants