Repository navigation
release: prepare cChardet 2.4.0 - #178
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.
Summary
Prepare cChardet 2.4.0 for release.
2.4.0Highlights
Wheels for this release cover CPython 3.11–3.15 plus free-threaded 3.14t/3.15t on manylinux x86_64/aarch64, Windows x86/AMD64/ARM64, and macOS x86_64/arm64. That is 49 wheels plus the sdist.
Local validation
All checks below ran with CPython 3.15.0 final:
make checkuv lock --checkpasseduv buildproducedcchardet-2.4.0.tar.gzand a 2.4.0 wheeltwine checkpassed for both distributionscchardet.__version__ == "2.4.0"andcchardet.version == (2, 4, 0)detect(),detect_all(), incrementalUniversalDetector, and thecchardetectCLI (plain and--json) on Shift_JIS inputAfter merge, create and push a signed
v2.4.0tag. The tag workflow builds the sdist and all platform wheels, verifies that the tag matches the package version, waits for approval at the protectedpypienvironment, and publishes through Trusted Publishing with attestations.