PSA: For reasons unknown, Github keeps reverting the 1.5.0 release to draft. [Fixed?]
14d 10h ago by dubvee.org/u/ptz in tesseract@dubvee.orgI have no idea why, but Github keeps reverting the 1.5.0 release to draft. I've had to re-publish it 5 or more times and it just keeps going back to draft.
Finally I just deleted the release and did an entirely new one. Fingers crossed.
If you're subscribed to release notices, I apologize if you may have been spammed by that. I'm just as annoyed with Github as you are.
The main work is in Codeberg now, but I'm still mirroring to Github and using it for releases as people are subscribed to them there. It's also got the Actions which perform the builds as well as the container registry. I don't strictly need the builds, but that would mean I'd have to get rid of the arm64 images as I can't build those locally (unless I want to do the builds on a Pi).
I also don't have a replacement container registry, either.
So, if someone has any suggestions for a CI builder and container registry, I'm open to ideas. I self-host most of my infra, but don't want to deal with adding those onto it.
Update: Seems to be related to the mirroring from Codeberg. Every time I push to the 1.5.1 branch, Codeberg mirrors that over, and Github moves the 1.5.0 release back to draft. What the actual fuck?
Anyway, I've disabled the mirroring and will just manually push to Github when it's time to do a release.