RELEASE 0.3.0

[burtenshaw]

Summary

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation
• New environment
• Refactoring

Alignment Checklist

Before submitting, verify:

• I have read .claude/docs/PRINCIPLES.md and this PR aligns with our principles
• I have checked .claude/docs/INVARIANTS.md and no invariants are violated
• I have run /pre-submit-pr (or bash .claude/hooks/lint.sh and tests) and addressed all issues

RFC Status

• Not required (bug fix, docs, minor refactoring)
• RFC exists: #___
• RFC needed (will create before merge)

Test Plan

Claude Code Review

[greptile-apps]

Greptile Summary

This PR bumps the openenv-core package version from 0.2.3 to 0.3.0 in pyproject.toml. It is a single-line change with no other file modifications.

• The entire PR description template is blank — no summary, no type-of-change checked, no test plan, and the alignment checklist is fully unchecked.
• INVARIANTS.md requires that breaking changes be documented in release notes even pre-1.0; a minor version increment implies new features or breaking changes, but nothing documents what is in this release, making invariant compliance unverifiable.

Confidence Score: 3/5

The file change itself is a safe one-line version bump, but the PR provides no documentation of what 0.3.0 contains, making it impossible to assess whether the broader release is safe to ship.

The actual diff touches one line and cannot introduce a bug on its own. The risk is what it represents: a minor version release with a completely blank PR description, an unchecked alignment checklist, and no release notes or changelog entry. The project's own invariants require pre-1.0 breaking changes to be documented, and a jump from 0.2.x to 0.3.0 typically signals substantive changes — none of which are visible here for review.

pyproject.toml is the only changed file and is trivially safe on its own; what needs attention is the missing release documentation that should accompany any version bump to 0.3.0.

Important Files Changed

Filename	Overview
pyproject.toml	Version bumped from 0.2.3 to 0.3.0; no other dependency or metadata changes

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["PR: RELEASE 0.3.0\n(pyproject.toml version bump)"] --> B{Pre-1.0 project?}
    B -- Yes --> C["Breaking changes acceptable\nif documented in release notes\n(INVARIANTS.md)"]
    B -- No --> D["Strict semver enforcement\nMAJOR / MINOR / PATCH"]
    C --> E{Release notes / CHANGELOG\npresent in PR?}
    E -- No --> F["⚠ ALIGNMENT FLAG\nMissing documentation of\nwhat changed in 0.3.0"]
    E -- Yes --> G["✅ Acceptable merge"]
    F --> H["Alignment checklist\nalso unchecked in PR template"]

Loading

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
pyproject.toml:7
**ALIGNMENT FLAG: Missing release documentation**

The PR alignment checklist is entirely unchecked and the description contains no summary, no type-of-change selection, and no test plan. `INVARIANTS.md` states: *"Pre-1.0: Breaking changes acceptable if documented in release notes."* A minor version increment (0.2.3 → 0.3.0) implies new features or breaking changes per the project's own semver guidance, but nothing documents what changed. Without that, it is impossible to verify that invariants (Gymnasium API signatures, client-server separation, rewards-inside-environment) were not violated by the broader set of changes this version bump represents.

**ALIGNMENT FLAG**: Missing 0.3.0 release notes / changelog
- **Principle at stake**: Pre-1.0 breaking changes require documentation (INVARIANTS.md — Breaking Change Policy)
- **The concern**: Version is bumped to 0.3.0 with no description of what changed, making it impossible to audit invariant compliance for this release
- **Suggested reviewer**: `@darktex`

_{Reviews (1): Last reviewed commit: "chore: release openenv-core 0.3.0" | Re-trigger Greptile}

[greptile-apps]

ALIGNMENT FLAG: Missing release documentation

The PR alignment checklist is entirely unchecked and the description contains no summary, no type-of-change selection, and no test plan. INVARIANTS.md states: "Pre-1.0: Breaking changes acceptable if documented in release notes." A minor version increment (0.2.3 → 0.3.0) implies new features or breaking changes per the project's own semver guidance, but nothing documents what changed. Without that, it is impossible to verify that invariants (Gymnasium API signatures, client-server separation, rewards-inside-environment) were not violated by the broader set of changes this version bump represents.

ALIGNMENT FLAG: Missing 0.3.0 release notes / changelog

• Principle at stake: Pre-1.0 breaking changes require documentation (INVARIANTS.md — Breaking Change Policy)
• The concern: Version is bumped to 0.3.0 with no description of what changed, making it impossible to audit invariant compliance for this release
• Suggested reviewer: @darktex

Context Used: .claude/docs/INVARIANTS.md (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: pyproject.toml
Line: 7

Comment:
**ALIGNMENT FLAG: Missing release documentation**

The PR alignment checklist is entirely unchecked and the description contains no summary, no type-of-change selection, and no test plan. `INVARIANTS.md` states: *"Pre-1.0: Breaking changes acceptable if documented in release notes."* A minor version increment (0.2.3 → 0.3.0) implies new features or breaking changes per the project's own semver guidance, but nothing documents what changed. Without that, it is impossible to verify that invariants (Gymnasium API signatures, client-server separation, rewards-inside-environment) were not violated by the broader set of changes this version bump represents.

**ALIGNMENT FLAG**: Missing 0.3.0 release notes / changelog
- **Principle at stake**: Pre-1.0 breaking changes require documentation (INVARIANTS.md — Breaking Change Policy)
- **The concern**: Version is bumped to 0.3.0 with no description of what changed, making it impossible to audit invariant compliance for this release
- **Suggested reviewer**: `@darktex`

**Context Used:** .claude/docs/INVARIANTS.md ([source](https://app.greptile.com/review/custom-context?memory=dbd1ab5e-bd4d-4701-9de0-9817404155a9))

How can I resolve this? If you propose a fix, please make it concise.