MacOS 11 PyPI publish fails consistently for 3.13 and 3.14

[ChristopherRabotin]

Hi there,

I'm at a loss... nearly every time I try to release my Python library with maturin, one of the packages is refused by PyPI, which causes me to spend hours trying to fix a release. I've tried switching to uv but that also does not work.

Today's issue is with the MacOS 11 Python 3.13 builds.

• Initially the MacOS 11.0 Python 3.12 was rejected with a 400 error
• Then MacOS 11.0 Python 3.13 seemingly had the wrong name ... but the 3.12 was accepted after I reverted to the release code of my other library that worked perfectly not 24 hours prior.
• Then that same wheel was corrupted after I switched all of my builds to be on Python 3.12.
• Then trying to switch from no compression to the zstd compression was an error because zstd is not supported by PyPI ... I had switched to the no compression approach because the compression was repeatedly corrupted back in August.

What can I do here? I'm on my fifth attempt in two hours to release the Python package ... is this a PEBKAC? Or is this PyPI changing its accepted formats regularly? Or is it maturin being unstable for MacOS releases?

Any hint is appreciated, thanks

[messense]

Sorry for the late reply, you can try to run twine check on these problematic wheels to see if there are any errors.