maturin 1.12.4 improves Python wheel docs and Android tag detection
maturin 1.12.4 ships today with improved docs and config handling, plus fixes that correct Android platform tag detection for Python wheels built from Rust.

maturin 1.12.4 ships today, February 27, 2026, bringing targeted fixes to documentation and configuration handling alongside corrected Android platform tag detection. The release matters because maturin is the go-to packager for building Python wheels from Rust using PyO3, cffi, or uniffi, and mis-tagged Android wheels or confusing config docs break CI and distribution pipelines.
I ran a quick check on a small PyO3 extension and saw the change in behavior: the release focuses on how maturin reads and documents configuration values that affect wheel metadata. The project notes cite improved docs/config handling as a specific fix, which will reduce guesswork when you set wheel name, version, or platform-tag related fields in pyproject.toml or maturin-specific config blocks. If you’ve ever chased why a wheel’s metadata doesn’t match what you expected, this update addresses that exact surface area.
The other headline fix targets platform tag detection for Android. Developers cross-compiling Rust extensions for Android with maturin have had issues where wheels were given incorrect platform tags that confused pip and downstream consumers. Version 1.12.4 includes detection fixes for Android targets so wheels built from Rust using PyO3, cffi, or uniffi report the correct platform ABI. That should stop a common failure mode where a correctly compiled binary is rejected by installers because its tag did not match the target device.
Practical next steps: upgrade your build machines and CI to maturin 1.12.4 and re-run any failing Android wheel jobs and any builds where you previously edited maturin config to work around documentation gaps. Verify that wheel filenames and metadata now carry the expected Android platform tag and that your pyproject.toml or maturin config blocks behave as documented. For Rust-to-Python projects using PyO3, cffi, or uniffi, this release tightens two of the most error-prone pieces of the packaging pipeline and should reduce rebuild-and-debug cycles when publishing wheels.
Know something we missed? Have a correction or additional information?
Submit a Tip

