release: 0.1.2#12
Merged
Merged
Conversation
The ``v0.1.1`` tag was cut at an earlier commit that did not include the 0.1.0 hardening PR or the subsequent replay/revocation fixes, and the tag + PyPI release happened before the security work landed on main. We cannot re-tag ``v0.1.1`` because git/pip cache the prior resolution; the only safe path is to skip the version and cut ``v0.1.2`` covering every hardening commit that's landed on main since ``v0.1.0``. - pyproject.toml: ``0.1.1`` → ``0.1.2`` - CHANGELOG.md: move the Unreleased block under ``[0.1.2] — 2026-04-22`` with a note that ``v0.1.1`` should not be used - SECURITY.md Changelog: collapse the two hardening passes into a single ``v0.1.2`` entry grouped by concern (replay, cache, metagraph, ergonomics, docs); preserve ``v0.1.1`` as a stub pointing at ``v0.1.2`` so anyone reading the file understands why a version is missing No code changes. 250 tests still pass.
shardi-b
approved these changes
Apr 22, 2026
shardi-b
left a comment
shardi-b
left a comment
There was a problem hiding this comment.
Approved. No issues found during code review.
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
2 participants
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.
Description
Cuts 0.1.2 covering both hardening PRs (#10 + #11). Skipping 0.1.1 because that tag already exists on origin + PyPI, pointing at a commit from before any of the hardening landed. Per our "don't re-tag" rule (git and pip caches retain the prior tag resolution), the only safe fix is to bump past it.
Changes Made
pyproject.toml: version0.1.1→0.1.2.CHANGELOG.md: moved the[Unreleased]block under[0.1.2] — 2026-04-22with a note thatv0.1.1should not be used.SECURITY.mdChangelog: collapsed the two hardening passes into a singlev0.1.2entry grouped by concern (replay/session, cache/atomicity, metagraph/integrator, operator ergonomics, documentation). Kept av0.1.1stub explaining why the version is missing.Issue Link
Testing
Automated Testing
Test Command(s):
All 250 tests pass; this PR is docs + version bump only.
Documentation
Checklist
Additional Notes
Once merged, tag
v0.1.2at the merge commit on main and push —publish.ymltriggers onv*tag push and will build + publish via the existing OIDC trusted publisher config.