Repository navigation
Release 0.2.0 (verification-policy wrapper) - #11
Merged
Merged
Conversation
Version 0.1.0 -> 0.2.0 (pyproject + __version__); CHANGELOG entries move from [Unreleased] to [0.2.0] - 2026-10-20. The wheel workflow's pinned Axiomere core commit moves from the Spec 003 build commit to f685e58, the Axiomere 0.2.0 release commit (tag v0.2.0 in the core repo), per the deliberate-bump rule (RTE-11).
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.
Cuts the
axiomerePython wrapper 0.2.0:pyproject.toml,src/axiomere/__init__.py).[Unreleased]to[0.2.0] - 2026-10-20, with a fresh empty[Unreleased]above.release-wheels.yml: the pinned Axiomere core commit moves from the Spec 003 build commit (cc45299…) tof685e58a5670e29f706b6f0201ba0d8f1e5ab137— the Axiomere 0.2.0 release commit (tagv0.2.0in AXIOVEX/axiomere) — per the deliberate-bump rule (RTE-11). The pin comment now names the 0.2.0 release commit, and a dated CHANGELOG bullet records the move.The wrapper artifacts are built from this PR's merge commit, uploaded to PyPI, verified byte-identical by re-download, and only then tagged
v0.2.0at that same commit. No spec claims, frozen artifacts, or verdicts touched.