chore: bump version to 0.6.1.dev0 (post-release)

[cursor]

Automatic post-release bump after 0.6.0 was published.

Change: pyproject.toml version 0.6.0 → 0.6.1.dev0

The publish workflow's bump job published this branch but could not open the PR (GitHub Actions is not permitted to create or approve pull requests). Opening manually — same pattern as after 0.5.0 (#1195).

Publish run: https://github.com/huggingface/OpenEnv/actions/runs/35973627790

  

[cursor]

Duplicate of #1245 — only one of these should merge

Two dev-bump PRs were opened 21 seconds apart by two runs of the release
automation, and their trees are identical: git diff 8e730115 cursor/openenv-release-management-16d4 is empty, and each changes the same three
lines against main (pyproject.toml plus the openenv version entry in
envs/grid_world_env/uv.lock and tests/validation_runtime/uv.lock).

• #1244 (this one) is on bump/0.6.1.dev0, the branch publish-pypi.yml
  itself created and the name its post-release-bump job looks for and reuses on a
  retry.
• #1245 is the same change on the release run's own working branch, and is the
  one announced in #openenv-release.

Either is correct. I would keep #1245 since it has been announced and is being
watched to green, and close this one; if you would rather keep the canonical
bump/* branch, merge this and close #1245 instead. I cannot close either — this
automation gets Resource not accessible by integration on
closePullRequest — so this needs one human click.

Why the lockfile lines are here

publish-pypi.yml's post-release-bump job edits only pyproject.toml. Both
envs/grid_world_env and tests/validation_runtime resolve the root openenv
package from a local path, so their uv.lock files pin the project version. With
only the pyproject.toml edit, uv lock --check fails in both directories — I
reproduced that on b543bd18 before adding the two lines, and both directories now
pass uv lock --check and uv sync --frozen --all-groups --all-extras --dry-run.

Note that the green validate-env-locks check does not cover this: it filters
changed paths through rg, which is not installed on ubuntu-latest, so it logs
rg: command not found and exits 0 on every lockfile PR. That is still unfixed on
main and remains worth a one-line change (grep -E, or install ripgrep).

The deeper fix is to teach post-release-bump to update these two locks, otherwise
every future version transition lands the same stale state.

View PR

  

_{Sent by Cursor Automation: Release}