release: v0.20.0 — carl-studio + carl-core 0.2.0 (v0.10 parity to PyPI)#6
Merged
Conversation
Closes the v0.10 carl.camp parity arc and ships it to PyPI. carl-studio 0.18.3 → 0.20.0 (major-minor bump for the entitlements + AXON + slime + ledger surface). carl-core 0.1.2 → 0.2.0 (9 new error subclasses + set_global_forwarder seam in interaction.py). Bumps: pyproject.toml 0.18.3 → 0.20.0 src/carl_studio/__init__.py 0.18.3 → 0.20.0 packages/carl-core/pyproject.toml 0.1.2 → 0.2.0 packages/carl-core/src/carl_core/__init__.py 0.1.2 → 0.2.0 uv.lock regenerated CHANGELOG.md: full v0.20.0 entry under [0.20.0] — 2026-05-09 — v0.10 carl.camp parity. Lists every new module, error code, CLI command, test count, and cross-repo touch point. Existing [Unreleased] section preserved (covers v0.18 / v0.19 work that landed pre-merge). Tag push order (per CLAUDE.md release flow): 1. carl-core@0.2.0 2. v0.20.0 Subpackage tag MUST go first; pushing v0.20.0 before carl-core@0.2.0 publishes leaves carl-studio install-broken on PyPI (carl-core 404 at install time).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps + CHANGELOG for the v0.10 carl.camp parity arc landing on PyPI.
carl-studio: 0.18.3 → 0.20.0carl-core: 0.1.2 → 0.2.0After merge, the tag push order is carl-core@0.2.0 first, then v0.20.0 per the CLAUDE.md release flow doctrine — pushing the parent tag before the subpackage tag publishes leaves carl-studio install-broken on PyPI (carl-core 404 at install time).
Why 0.20.0 not 0.19.x
The v10 parity arc (entitlements + AXON + slime + ledger) is a major-minor surface addition. Skipping 0.19.x leaves room for the existing v0.19 WIP (anticipatory reward / training rewards) to release independently if/when ready. Versions are cheap; collisions are expensive.
Files changed
pyproject.tomlversion = "0.20.0"src/carl_studio/__init__.py__version__ = "0.20.0"packages/carl-core/pyproject.tomlversion = "0.2.0"packages/carl-core/src/carl_core/__init__.py__version__ = "0.2.0"uv.lockCHANGELOG.md[0.20.0]entry with full v10 surface inventory + cross-repo notesTest plan
git tag carl-core@0.2.0 && git push origin carl-core@0.2.0, wait for PyPI upload (gh run watch), thengit tag v0.20.0 && git push origin v0.20.0python -m venv /tmp/v20 && source /tmp/v20/bin/activate && pip install carl-studio==0.20.0 && carl --versionreturnscarl-studio 0.20.0python -c 'from carl_studio.entitlements import EntitlementsClient; print("ok")'succeeds (proves v10 surface is actually shipped)🤖 Generated with Claude Code