Release 0.13.0 - #82
Merged
Merged
Conversation
Six merged PRs of correctness and test-quality work, unreleased since 0.12.1. The user-facing change is fan_out: a node marked `fan_out: true` now dispatches once per element on all six runtimes, not just DBOS. The other five handed the whole upstream list to a single invocation, so the "one call per element" the IR describes was a fiction everywhere but one target, and judge signatures had to accept the batch. The rest is the suite's ability to catch regressions. Three mutation sweeps (64 mutations) found fifteen places where a real regression would have shipped green — per-node timeouts ignorable on two runtimes, DEFAULT_MODEL flippable to Opus at ~5x cost, an agent-side cost estimate that could be off by 1000x because it was only compared against itself. Every slow e2e suite now runs in CI (three of twenty-seven did), all seven checks are required, and a test can no longer spend inference tokens. Also bumps the three companion version files the suite pins against the package version, and repairs the CHANGELOG compare links, which had been stale since 0.9.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SBuSDL7Svm7iDzgmhTpDSW
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.
Cuts 0.13.0. Six merged PRs have been sitting unreleased since 0.12.1 — local and PyPI are both still on the old version.
What ships
fan_outdispatches per element on all six runtimes (#76). This is the one user-facing behavior change. It worked on DBOS only; the other five handed the whole upstream list to a single invocation, so the "one call per element" the IR describes was a fiction everywhere but one target, and a judge signature had to accept the batch. Which input is the fanned list resolves in the language-neutral_common.fan_out_element_param, because two adapters disagreeing about that would make onepipeline.yamlmean two different things.Everything else is the suite's ability to catch regressions (#77–#80). Three mutation sweeps, 64 mutations, fifteen gaps closed. Each was a real regression that could have shipped green: per-node
timeout:ignorable on Temporal and Cloudflare gates,DEFAULT_MODELflippable to Opus at ~5× cost, an agent-side cost estimate off by 1000× because it was only compared against itself,rote compilereporting success on a bad config. Plus: every slow e2e suite runs in CI (three of twenty-seven did), all seven checks are now required, and a test can no longer spend inference tokens.Housekeeping caught while cutting this
CITATION.cff,plugin/.claude-plugin/plugin.json,.claude-plugin/marketplace.json) — the suite pins these againstrote.__version__and correctly failed the bump until they matched.Release gates, run locally
pytest tests/ruff check+format --checkmypy src/rote(strict)scripts/sanity-check.shrote.__version__= 0.13.0rote 0.13.0rote emitfrom the installed wheelAfter merge:
git tag v0.13.0 && git push origin v0.13.0triggersrelease.yml(Trusted Publishing, no token secrets).🤖 Generated with Claude Code
https://claude.ai/code/session_01SBuSDL7Svm7iDzgmhTpDSW