Repository navigation
chore: prepare 0.1.9 maintenance candidate - #106
Merged
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
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.
Prepare the 0.1.9 maintenance candidate without publishing it.
Only the package's dynamic source version changes from 0.1.8 to 0.1.9. Dependency constraints, the lock, APIs and the historical migration comparisons remain unchanged. This administrative version change does not need a separate issue under the contribution policy.
The candidate includes the verified numerical, Polars and configuration repairs from #99–#103, the GitPython security fix from #93, documentation link-check reliability from #105, migration guides from #95, workflow pins from #96 and contribution routes from #98. The original @quantum-like contribution and its attribution remain in those owning PRs.
At reviewed head b1a5de1:
Current-head hosted supported CI and qualification must also pass before merging. Python 3.15 remains explicitly deferred under #45; support remains >=3.12,<3.15.
No release workflow, tag, PyPI publication or canonical website deployment is requested or executed by this PR. Those require a separate user decision after the final main candidate is verified.
AI assistance: Codex prepared the version-only change and ran the checks. The maintainer remains accountable for the change.