Bump version 1.1.1 -> 1.1.2#26
Merged
Merged
Conversation
Cut a release carrying the already-merged `numpy>=2` support (#25), so downstreams (e.g. neml2) can depend on a pyzag that no longer pins numpy<2. No code changes — version bump only (pyproject.toml + docs). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
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.
What
Version bump only:
1.1.1→1.1.2(pyproject.toml+docs/conf.py). No code changes.Why
requirements.txtalready declaresnumpy>=2(merged in #25 "numpy ver >= 2"), but the released1.1.1still effectively pinsnumpy<2for anything that depends on it. Cutting1.1.2publishes a pyzag that no longer constrains numpy below 2.Downstream: this unblocks
neml2from depending on a pyzag that dragsnumpy<2into everypip install neml2— which currently downgrades numpy on Google Colab and conflicts with Colab'snumpy>=2packages (opencv, jax, …). Once1.1.2is on PyPI, neml2 will bump its pin topyzag==1.1.2.Release
After merge: create a GitHub Release/tag for
v1.1.2to trigger thepython.ymlPyPI publish.🤖 Generated with Claude Code