Skip to content

Prepare op_engine 0.4.0 release - #190

Merged
jc-macdonald merged 2 commits into
mainfrom
chore/prepare-0.4.0
Oct 3, 2026
Merged

jc-macdonald merged 2 commits into
mainfrom
chore/prepare-0.4.0

Conversation

@jc-macdonald

Copy link
Copy Markdown
Member

Summary

  • Prepare op-engine and flepimop2-op-engine 0.4.0.
  • Require the matching 0.4.0 core from the provider, and raise its optional op_system integration floor to 0.6.0 (flepimop2-op-system>=0.6.0, op-system>=0.6.0).
  • Point the development op_system pins at the op_system 0.6.0 release preparation (op_system #253, 89c34a6).
  • Cut the accumulated changelog entries since 0.3.0 into the 0.4.0 section.

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.0 baseline.

Changelog edits

Release order

  1. Merge op_system #253 and publish op_system 0.6.0.
  2. Move this PR's two op_system pins from 89c34a6 to #253's merge commit. I can do this.
  3. Merge this PR and run the op_engine release workflow.

The op_engine release workflow runs just build-all. Its provider clean-room suite resolves the lowest published dependencies, so it needs op-system 0.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 exact op-engine==0.4.0 provider requirement.
  • UV_PYTHON_VERSION=3.13 just build-check build-test-core: both wheels pass twine check --strict, and the clean core wheel suite passed (579 passed, 2 skipped).
  • Not yet run: build-test-provider, which needs op_system 0.6.0 on PyPI.

🤖 Generated with Claude Code

jc-macdonald and others added 2 commits October 2, 2026 20:50
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>
@jc-macdonald
jc-macdonald merged commit 28f4463 into main Oct 3, 2026
6 checks passed
@jc-macdonald
jc-macdonald deleted the chore/prepare-0.4.0 branch October 3, 2026 01:08
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