Repository navigation
Conversation
The publish workflow takes this section verbatim as the GitHub Release body and fails without it, so it lands before the tag. Drafted from the 19 commits since v1.8.7, then written for a user of the packages: the two changes that ask something of them come first, preset lengths in voxels and Generic_Rigid's affine.
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Breaking changes CHANGELOG.md |
The notes describe changes to preset length units, FireANTs learning rates, and Generic_Rigid transform output. |
Features CHANGELOG.md |
The notes cover transform declarations and readers, 2-D and remote registration, initialization, workflow schemas, safetensors, and Python 3.14. |
Fixes CHANGELOG.md |
The notes cover OME-Zarr fields and outputs, moved-image storage, multi-time-point input, resampling, and app requirement installation. |
Estimated code review effort: 1 (Trivial) | ~3 minutes
Change: Other
Possibly related PRs
- fideus-labs/KonfAI#304: Implements affine registration outputs and consumers described in the changelog.
- fideus-labs/KonfAI#280: Implements the preset-length unit change and updates pinned presets.
- fideus-labs/KonfAI#303: Implements OME-Zarr displacement-field output and axis and unit handling.
Merge Risk: 
36ef7
-
The release-note clarification addresses the identified ambiguity. No remaining issue prevents merging after normal checks.
Pre-merge checks: 
-
Check name Status Explanation Title check The title "ci: prepare v1.8.8 release" follows Conventional Commits and names the main change: preparing the v1.8.8 release. The changeset adds the v1.8.8 changelog entry only, with no runtime or pack… Description check The description covers the release-note purpose, base commit, validation steps, and the explicitly unrun perf-check. It omits the template's Type of change selection, the Related issues section, and t… Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Title check
-
Explanation
The title "ci: prepare v1.8.8 release" follows Conventional Commits and names the main change: preparing the v1.8.8 release. The changeset adds the v1.8.8 changelog entry only, with no runtime or package version changes, so the title is related to the change. It is not generic. It does not mention the release notes content, which is an acceptable level of detail. The title is slightly broad because the 'ci' type does not match a changelog-only commit exactly, but the title still describes the real change.
Full details: Description check
-
Explanation
The description covers the release-note purpose, base commit, validation steps, and the explicitly unrun perf-check. It omits the template's Type of change selection, the Related issues section, and the Breaking changes & migration section, even though the changelog documents breaking changes to preset length units and Generic_Rigid transform output. The How has this been tested section lists commands and observations, and the checklist items are not ticked. The description is mostly complete on substance but misses several template sections.
Resolution
Consider adding: (1) the Type of change selection (ci/build or chore), (2) a Related issues entry or deletion of that section, (3) a Breaking changes & migration section that summarizes the preset length unit and Generic_Rigid transform output changes, since the changelog documents them, and (4) the checklist state for pixi run check and the other test commands.
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
A rabbit reads the release notes at dawn,
New transform shapes are carefully drawn.
Voxel steps and schemas appear,
Safetensors hop into gear.
OME-Zarr fields find their way,
The rabbit thumps: “Ship notes today!”
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
The writer declares the RFC-5 entry on an axis-aligned grid alone. RFC-5 places a field by a scale and a translation, so an oblique grid keeps its rotation in a sidecar only KonfAI reads, which the release note implied otherwise.
Release notes for 1.8.8, from main at 3a14b2f. The section describes the user-visible changes and migrations; earlier sections are preserved byte-for-byte. No runtime or package version file changes.
Validation so far:
release_notes.py v1.8.8reads the section, classifies the tag as stable, andtests/unit/test_release_notes.pypasses.pip installof the public tutorial's requirements, its four notebooks with the published presets (0 errors, correlation -0.06 to 0.90, nuclei Dice 0.00 to 0.92,pair.ozx42 MB).Transform.h5is anAffineTransform,--set transform_type=fieldgives the field back, an ensemble and--ttarefuse the affine by name,evalreads it.app.jsonnames are present as.safetensors, and the 99 published configs validate against the schema of this commit.Not run:
pixi run perf-check. Other jobs hold the machine (load average above 25), and its gate refuses to time there.Summary by CodeRabbit
Generic_Rigidtransform output.