chore: release v0.12.1 - #329
Merged
Merged
Conversation
jayhesselberth
force-pushed
the
release-v0.12.1
branch
from
September 15, 2026 13:58
094ebe8 to
17ef74a
Compare
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
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.
Summary
Patch release bundling three bug fixes merged since v0.12.0:
optimize'sbest_params.jsonincludesselection_metric, whichtrain --model-configrejects #324) —leech model train --model-configno longer crashes onleech model optimize's ownbest_params.jsonoutput (selection_metricis now dropped before model construction)data mergepairwise relabeling matches by originallabelsvalue, silently collapsing same-body contrasts to one class #323) —leech data mergepairwise relabeling now tracks chunk provenance by source file instead of matching on original label values, fixing a silent same-class collapse when two input files share an internal labeldata preparecounts BAM reads absent from a pre-filtered POD5 as failures, aborting via MAX_FAILED_READ_FRACTION #325) —leech data prepareno longer misclassifies reads absent from a pre-filtered POD5 as failures, and theMAX_FAILED_READ_FRACTIONcheck is now measured over reads actually attemptedVersion bumped 0.12.0 → 0.12.1 in all three declared locations (
pyproject.toml[project] version,pyproject.toml'sleech-core==pin,rust/Cargo.toml),CHANGELOG.mdassembled fromchangelog.d/fragments via towncrier (added missing fragments for #326/#327; #325 already had one).Test plan
/check:ruff format --check,ruff check,snakefmt,ty check— all clean/docs: full documentation audit,zensical build— passes, no changes neededrust/build.shrebuilt and reinstalledleech_core0.12.1;check_rust()reports no version mismatchuv.lock/rust/Cargo.lockdiffs are single-line version bumps only (no emscripten churn)After merge, the release is finalized by tagging
mainwithv0.12.1and pushing the tag, which triggers.github/workflows/release.ymlto build wheels/sdists and publish to PyPI.🤖 Generated with Claude Code