chore(release): bump version 0.12.0 to 0.12.1 - #254
Merged
Conversation
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.
Bumps all 8 version locations 0.12.0 → 0.12.1 and writes the release notes.
Patch is what
cz bumpdetects — every commit sincev0.12.0isfix/docs/test, with nofeat:and noBREAKING CHANGE. The one API addition,symmetrize(mode=...)and the matching argument onfnp.random.symmetric, is a new optional keyword with the previous behaviour as its default, so it is backward compatible.The notes are assembled, not generated.
update_changelog_on_bump = true, socz bumprewrote## Unreleasedinto a single bullet and would have dropped the billing-impact and symmetry prose. That prose is restored abovecz's generated commit list, per the existing format.One correction to the pending notes is included (
898ba0fadc). They had carried over the standard line that the release "ships as a new version opening a new phase, so no submission is re-evaluated against it". That is not true here: this one lands inside the current phase rather than opening one. The claim is replaced with the measured result — no already-scored submission in the current phase passes a non-scalarfill_valuetofull/full_like, so none is repriced.Verified: all 8 version locations at 0.12.1, three lockfiles refreshed and
uv lock --checkclean on all three, 10,365 tests pass, ruff and pyright clean, gitlint clean over the range.No tag is pushed by this PR. Tagging triggers the PyPI publish workflow and is a separate, deliberate step.