Prepare the v0.3.0 changelog - #68
Merged
Merged
Conversation
Closes the Unreleased section and dates it. Entries are reordered so the two API changes sit together near the top, since they are what anyone upgrading needs to read. Two corrections while closing it out. The security entry claimed 76 advisories, which was a mid-work count taken from the lockfile rather than the final state; GitHub now reports every advisory resolved, so the number is dropped in favour of saying so. A Fix entry is added for the spelling corrections in IKTOD's class docstring and the IKGOD usage example, which are user-facing documentation and were not recorded.
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.
Closes the Unreleased section and dates it 2026-08-16.
Why v0.3.0
Two API changes, both breaking for older environments:
numba,numpy,scikit-learnraised to 0.63.0, 2.3.2, 1.7.2On a 0.x version, a minor bump is how that gets signalled. Last release was v0.2.4.
Changes while closing it out
Entries are reordered so the two API changes sit together near the top — that is what anyone upgrading needs to read first.
Two corrections:
Deliberately left out: the internal-only work from this batch — CI restructuring, the pre-commit repair, removal of the unused
cluster/_utils.pyandpixi.lock. None of it is observable to anyone installing the package.After this merges
Tagging
v0.3.0triggerspypi.yml, which publishes to PyPI and creates a GitHub Release, anddeploy-gh-pages.yml, which deploys versioned docs and moves thelatestalias. A PyPI version number can never be reused, so that step should be taken deliberately rather than as a follow-on.Verification
mkdocs build --strictpasses, so the changelog page renders. All six pre-commit hooks pass.