chore(release): 1.6.0 — ship simulator tools to PyPI#103
Merged
Conversation
The ``process_improve.simulation`` module landed on main in #101 (``e174826`` - "Add fake-data simulator tools (create/simulate/ reveal)") but hasn't been released to PyPI yet. This bumps ``pyproject.toml`` from 1.5.1 to 1.6.0 so the publish workflow (.github/workflows/publish.yml) picks it up and tags v1.6.0. MINOR bump is correct per CLAUDE.md: a new module (simulation/) with a new public API (create_simulator / simulate_process / reveal_simulator tool_spec registrations). Downstream: factorial's ``test_simulator_flow.py`` currently skips the three ``test_loop_*`` integration tests because the registry on PyPI 1.5.1 doesn't carry the simulator tool names. Once this release ships, factorial can bump its ``process-improve>=1.4.0`` pin and drop the ``requires_simulator_tools`` skip guard. - ``pytest -o "addopts=" -q`` -> 777 passed, 10 skipped - ``ruff check .`` -> clean - ``tests/test_simulation.py`` -> 27 passed, simulator tools register and dispatch cleanly through ``execute_tool_call``. https://claude.ai/code/session_01EL8jKS3jBcSBdk6HK8n2wq
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
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
Release PR — bumps
pyproject.tomlfrom1.5.1→1.6.0so the publish workflow shipsprocess_improve.simulation/to PyPI.The module itself landed on
mainin #101 (e174826— "Add fake-data simulator tools (create/simulate/reveal)") but the pinned PyPI version hasn't moved, so anyone pip-installingprocess-improvetoday still gets 1.5.1 withoutsimulation/.Per
CLAUDE.md:@tool_specregistrations (create_simulator,simulate_process,reveal_simulator).pyproject.tomlversion changes onmainand creates thev1.6.0tag + GitHub release.Why now
The downstream
factorialbackend has a test-skip guard (requires_simulator_toolsintests/test_simulator_flow.py) that short-circuits three integration tests because the installedprocess-improve(1.5.1 from PyPI) doesn't register the simulator tool names. Once this release ships, factorial can bump itsprocess-improve>=1.4.0pin to>=1.6.0and drop the skip guard — follow-up PR already queued.Test plan
uv run ruff check .— cleanuv run pytest -o "addopts=" -q— 777 passed, 10 skipped, 0 failedtests/test_simulation.py— 27 pass; simulator tools register and dispatch throughexecute_tool_callend-to-enduv.lockintentionally not committed (perCLAUDE.mdlock-file rule)publish.ymlrun on merge creates thev1.6.0tag + PyPI releasefactorialfollow-up PR will bump the pin and drop the skiphttps://claude.ai/code/session_01EL8jKS3jBcSBdk6HK8n2wq
Generated by Claude Code