Prepare op_engine 0.4.0 release - #190
Merged
Merged
Conversation
Bump op-engine and flepimop2-op-engine to 0.4.0, require the matching core from the provider, raise the optional op_system integration floor to 0.6.0, and cut the accumulated changelog entries into the 0.4.0 section, adding entries for forcing-aware tau-leaping, producer forcing, bounded thinning SSA, and the renewal-birth fix that had none. The development op_system pins point at the op_system 0.6.0 release preparation; move them to its merge commit once it is released. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Move the development op_system pins from the release preparation branch to the v0.6.0 release commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
op-engineandflepimop2-op-engine0.4.0.op_systemintegration floor to 0.6.0 (flepimop2-op-system>=0.6.0,op-system>=0.6.0).89c34a6).The provider's development flepimop2 source remains pinned to the reviewed tip of Flepimop2 PR #348. Published wheels continue to support the released
flepimop2>=0.3.0baseline.Changelog edits
Release order
89c34a6to #253's merge commit. I can do this.The op_engine release workflow runs
just build-all. Its provider clean-room suite resolves the lowest published dependencies, so it needsop-system0.6.0 on PyPI first.Validation
just ci: 592 core tests passed, 2 skipped. 379 provider tests passed. Ruff and strict mypy passed for both packages.just docs: strict documentation build passed.just release-check: release version 0.4.0 validates, including the exactop-engine==0.4.0provider requirement.UV_PYTHON_VERSION=3.13 just build-check build-test-core: both wheels passtwine check --strict, and the clean core wheel suite passed (579 passed, 2 skipped).build-test-provider, which needs op_system 0.6.0 on PyPI.🤖 Generated with Claude Code