Skip to content

Finish the 0.3.0 version bump; RELEASING.md follow-ups - #24

Merged
scosman merged 2 commits into
mainfrom
claude/exciting-davinci-mjvvcu
Oct 17, 2026
Merged

scosman merged 2 commits into
mainfrom
claude/exciting-davinci-mjvvcu

Conversation

@scosman

@scosman scosman commented Oct 17, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #23, which was merged before these commits were ready.

Summary

Finish the 0.3.0 version bump (345fa0f):

  • The v0.3.0 bump commit changed only pyproject.toml and uv.lock. src/seahaven_stripe_world/world.py and openenv.yaml now also say 0.3.0.
  • The fixtures keep the world_version they were frozen at.
  • New test test_the_version_agrees_in_all_four_places in tests/test_package.py. It fails unless all four places agree, so a bump that misses one fails CI. Against the old tree it fails and names world.py and openenv.yaml.

RELEASING.md follow-ups (7c0e58c):

  • uv.lock is never edited by hand. The table in section 1 has a new "Written by" column. The text says uv writes the lock: uv version during a bump, and uv lock or uv sync after any other pyproject.toml change.
  • --extra serve on every command that needs it.
    • openenv, hf and huggingface_hub are installed only by the serve extra, and a plain uv sync removes that extra. Run without it, the Space-card command failed with ModuleNotFoundError: No module named 'huggingface_hub'.
    • Every such command now runs as uv run --extra serve …: openenv validate, hf auth login, openenv push, the Space-card python -c and the Space test snippet.
    • Section 3 explains why. The separate uv sync --extra serve step is gone, and the doc still says the extra needs Python 3.14 final.

Note: PyPI's seahaven-stripe-world==0.3.0 was built before this fix and still reports world.version == "0.2.0". The next release (0.3.1 or later) fixes that.

Test plan

  • uv run ruff format --check && uv run ruff check, uv run ty check, uv run seahaven check: clean
  • uv run pytest: 1300 passed, 2 skipped
  • small_co loads under world version 0.3.0 with its fixture still at world_version: 0.2.0
  • In a fresh clone after a plain uv sync, the ModuleNotFoundError and Failed to spawn: openenv errors reproduce. With --extra serve, all of these work:
    • openenv validate . (only the expected missing-validation: failure)
    • hf auth login --help
    • openenv push --help
    • from huggingface_hub import metadata_update
    • from openenv import AutoEnv
  • uv publish and openenv push were not run, since they publish

Generated by Claude Code

scosman and others added 2 commits October 17, 2026 17:43
The v0.3.0 bump updated pyproject.toml and uv.lock, which `uv version`
writes, but not world.py's `version=` or openenv.yaml's `version:`, which
are set by hand. Both now say 0.3.0. The fixtures keep the world_version
they were frozen at.

tests/test_package.py now checks that all four places agree, so a bump
that misses one fails the check list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FVqE8sQ6jvyHDJJjQ1yaWK
…xtra commands

- Section 1 says uv.lock is never edited by hand. `uv version` writes it
  during a bump, and `uv lock` or `uv sync` after any other pyproject.toml
  change. The table gets a "Written by" column, and the text points to the
  test that fails unless all four places agree.
- openenv, hf and huggingface_hub come only from the serve extra, and a
  plain `uv sync` removes that extra. So every command that runs one of
  them now uses `uv run --extra serve`: openenv validate, hf auth login,
  openenv push, the Space-card `python -c` (which failed with
  ModuleNotFoundError: huggingface_hub) and the Space test snippet.
  Section 3 explains why, and drops the separate `uv sync --extra serve`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FVqE8sQ6jvyHDJJjQ1yaWK
@scosman
scosman merged commit e34b2c9 into main Oct 17, 2026
1 check passed
@scosman
scosman deleted the claude/exciting-davinci-mjvvcu branch October 17, 2026 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant