@kyamagu ah, sorry about this - now it is failing because some of the wheels already exist on pypi . I remember in v87.x, you were able to "re-release" at some point, adding a few wheels (and overwriting recent uploads?). How do you do that? googling seems to suggest that even if i login on pypi to remove the older v144.0 wheels, I must bump some number on this side?

@kyamagu apologies I have pushed a new .post1 tag and release on that, basically an anonymous short branch to bypass needing your explicit review/approval to push onto main. Sorry about that. It is not as bad as it sounds - v87 branch I can do everything/release. I'll include the. post1 tag in the next pull either as a rebase or a side-pull, so that it is available from future main as an ancestor. Hope you don't get mad about this. Adding a ".postN" seems to be the simplest recommended practice.

Cc @theacodes @talmo

@kyamagu @theacodes @talmo the post1 builds seem to be failing with some (transient) networking issues about 429 too many requests within the CI infrastructure . I 'll just restart the failed builds tomorrow morning and hope the problem goes away. Sorry for the wait /noise .

Found a filing pypa/cibuildwheel#2765 , which was filed 10 hours ago and closed. The solution seem to suggest upgrading the cibuildwheel version in the ci . I seem to remember we split up and use TWO old cibuildwheel versions for a reason @kyamagu @theacodes @talmo I'll read that issue properly as well as our log when I wake up properly... (middle of night and not yet morning here)