Closed cadesalaberry closed 1 year ago
It's completely run automatically. It seems that there have been a few failures that require the attention of a core developer. I'll have a look in the coming week(end).
There's no other steps to support 2022.1.17f1.
For image status see our image status page.
Leaving this open until resolved.
Mmm, the new version editor-2022.1.18f1-1.0.1
which was released today also seems to be stuck.
Could I help in any way ?
Yea, all of them will be stuck until we unblock the automated pipeline.
It has a safety stop for if something goes wrong. There's a max amount of failures that usually isn't reached, and now it has.
editor-2021.3.11f1-1.0.1
is stuck too.
Automated pipeline for building the images has been restored. Expect your images in the coming 24 hours.
I see that the version 2022.1.16.f1 has its docker images built, but not the version 2022.1.17f1.
What can I do do contribute and have it pushed to the docker hub?
It seems that there is a Github action to run to add a new version, but I can't run it on my side.