release: v0.3.0 - #67
Merged
Merged
Conversation
Rolls up everything since v0.2.0: the crash-resumable moat, proven and polished — resume_run, the kill-9 resume demo, exact-once budgets across a mid-step crash, and a crash-resume guide — plus the `riskkernel init` on-ramp. Also makes the SDK install clean. The SDK is now published to PyPI, so `pip install riskkernel` replaces the from-source git URL everywhere: the README, the init template, the example requirements, and the SDK README. Version markers bumped per the checklist: the CHANGELOG rolled into 0.3.0, the SDK to 0.3.0, version.go to 0.3.1-dev, and the VISION status line. No breaking API changes; forward-compatible with existing v0.2.x state.
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.
v0.3.0
Rolls up everything merged since v0.2.0 (#61–#66) and makes the SDK install clean.
Highlights
resume_run, thekill -9resume demo, exact-once budgets across a mid-step crash, and a crash-resume guide.riskkernel init— one-command on-ramp (.env+ a runnable example).pip install riskkernel, no git URL, no#subdirectory. Switched everywhere (README, theinittemplate, examplerequirements.txt, SDK README).No breaking API changes; forward-compatible with existing v0.2.x state.
Checklist files bumped
CHANGELOG.md→## [0.3.0] - 2026-06-06, compare links, fresh empty[Unreleased].0.3.0(pyproject+__init__);version.go→0.3.1-dev;docs/VISION.mdstatus line.After merge — tag the merged commit (PyPI publishes on the tag)
The pending trusted publisher is configured, so the tag fires three things: binaries, the cosign-signed image, and the PyPI publish.
Skipping the pull lands the tag on the previous commit and ships stale markers (it bit v0.1.1). Verify before pushing:
git show v0.3.0:sdks/python/pyproject.tomlreads0.3.0. Then, after the workflows finish:pip install riskkernelworks,docker run ghcr.io/prashar32/riskkernel:0.3.0 version, andcosign verify.