ghcr packages are stale! latest is v1.6.2 but v.1.9.0 in releases

[vitalyu]

Expected behavior (what you expected to happen):

Release version == Package version

[pratiyushpushkar05]

@juev @ldmonster Any update on this ? Why v1.9.0 or v1.9.1 is not pushed to docker.io ? This is the prime source where people would be pulling shell-operator from - https://hub.docker.com/r/flant/shell-operator

v1.6.2 is available -

docker pull ghcr.io/flant/shell-operator:v1.6.2
v1.6.2: Pulling from flant/shell-operator
56508f9ef54b: Download complete 
6e771e15690e: Download complete 
8baab3402b72: Download complete 
7d5d91362819: Download complete 
4b3566fce736: Download complete 
2a14f5c89dab: Download complete 
Digest: sha256:10aa9ca5936cac0fcd7cafb24d9d9fc2a89bdb684c3c33d8b036fc8065ce793b
Status: Downloaded newer image for ghcr.io/flant/shell-operator:v1.6.2

While v1.9.1 not available -

docker pull ghcr.io/flant/shell-operator:v1.9.1
Error response from daemon: failed to resolve reference "ghcr.io/flant/shell-operator:v1.9.1": ghcr.io/flant/shell-operator:v1.9.1: not found

Looks like some auto push is getting stuck .PTAL

[vladimirfx]

So, no more binary releases?

[allanger]

@ldmonster Hi, I hope you are the right person to mention here

I'm using the operator quite a lot, and wanted to ask whether you have any intention to maintain the gchr container build? It wouldn't be a problem for me to step in and write actions for it and maintain them as well, but I would like to make sure that it's going to get some attention when done.