libgit2
Release/Build process breaking consumers (wheels not available)
Hi, I just happened to install pygit2 1.17 (via indirect dependencies from poetry-git-version-plugin that specify >=1.15).
Currently, not all wheels are available, since the build is still running, but pypi already delivers the new version (without sources also). This breaks the installation for the whole period until the build finishes.
(Right now, only some Windows wheels are available, but none for Linux or MacOS)
I have no experience in uploading packages to the public pypi, but it seems it would make sense to first build all the wheels, and once all are ready, publish them in one step, so the amount of time the package exists in a broken state is minimized. (Unless pypi can somehow hide the new release before it is fully ready?)
Another alternative would be, to upload the wheels directly after they are built (and/or parallelize that, as is takes over 5h already), that still leaves some waiting/broken, but may reduce the time also.
And just as I post this, the build finishes and wheels are available ;) It still will become an issue again for the next release
I'm working to uniform the deployment process...
BTW, this issue is duplicate of #1340, but at least they closed that after the full deployment process completed (within an hour). FYI, its not very respectful to leave duplicate/resolved issues open on popular repos maintained by 1 person.
Feel free to close it - I was trying to point out, that the build/release process itself may be broken (and thus could repeat this issue again, if it has not been changed). If you already changed it, I apologize, I did not follow the changes (and did not see any reoccurrence so far, but this is also somewhat unlikely, as it requires trying to install exactly in that timeframe between the first upload of a new release, and the final ones).
Thank you for fixing this! The new process should avoid this issue now as much as possible.