Release v2.5.4 - #129
Merged
Merged
Release v2.5.4#129
Conversation
PyPI publishing is handled by a separate release process, so this workflow shouldn't be able to upload from the public repo when a GitHub release is published. Co-Authored-By: Claude Opus 5.5 (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
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.
Sets the version to 2.5.4 for a patch release containing:
sort_keys=True(Python 3.14, and unorderable keys on all versions) and a buffer leak on encoding errors; CI now tests 3.13 and 3.14Also removes
publish_pypi.yml. PyPI publishing is handled by a separate release process, so publishing the GitHub release shouldn't upload from this repo. This matches the same change in spaCy (26b4d1dc0).After merging, pushing the
release-v2.5.4tag builds the wheels and sdist into a draft GitHub release.馃 Generated with Claude Code