[scosman]

Summary

.github/RELEASING.md used to cover only the Hugging Face Space push. It now walks through the whole release in seven numbered steps:

1. Bump the version in all four places that hold it:

   • pyproject.toml and uv.lock, both set by uv version X.Y.Z
   • src/seahaven_stripe_world/world.py and openenv.yaml, both edited by hand

   The bump merges through a PR once the check list is green. Each fixture keeps the world_version it was frozen at, and the doc gives the reason (frozen_world_version, SH403).

2. Tag the merged main commit vX.Y.Z. First, grep the two hand-edited version fields to confirm they were changed.

3. Check the release from a fresh clone of the tag:

   • Run openenv validate.
   • Run uv build into a directory beside the clone. openenv push uploads everything except dot-files, so a dist/ inside the clone would end up on the Space.
   • List the contents of the wheel and the sdist.
   • Smoke-test the wheel in a throwaway environment, asserting that world.version matches the package version.

4. Publish to PyPI by hand with uv build and uv publish, using a project-scoped UV_PUBLISH_TOKEN. The doc covers:

   • A PyPI version can never be uploaded again; a fix means a new version, and the bad one can be yanked.
   • --check-url for retrying an upload that stopped partway.
   • Checking the release afterwards by installing it from PyPI.

5. to 7. Push to the Space, set the Space card, test the Space. Unchanged, except that they now run from the release clone. The Space's Dockerfile builds from the uploaded tree, not from PyPI. PyPI goes first only because it is the one step that cannot be redone.

The AGENTS.md line that points to RELEASING.md now says what it covers.

Heads-up: v0.3.0 shipped with only part of the version bump

372d2ce ("version bump for release", tagged v0.3.0) changed only pyproject.toml and uv.lock. world.py and openenv.yaml on main still say 0.2.0, so the published seahaven-stripe-world==0.3.0 wheel reports world.version == "0.2.0". This PR's post-publish check fails on 0.3.0 with AssertionError: 0.2.0. This PR does not fix that. PyPI won't accept a second 0.3.0, so the clean fix is a 0.3.1 release that follows this checklist.

Test plan

• uv run ruff format --check && uv run ruff check, uv run ty check, uv run pytest, uv run seahaven check: all pass
• Ran the bump procedure on a scratch clone. uv version changes only pyproject.toml and uv.lock; after the hand edits there are exactly four changed files. The suite and seahaven check pass with the fixtures left at their old world_version.
• Ran the clone, validate, build, list-contents and wheel smoke-test commands as written against v0.3.0.
• Ran the publish-check command against PyPI's 0.3.0; it fails with AssertionError: 0.2.0, which is how it caught the partial bump above.
• uv publish and openenv push were not run (they publish)

---

Generated by Claude Code