Image build process seems stuck at version 124

[asprega]

Describe the bug
Hi all. I'm not following the default issue template because this is not a bug with the container itself. I'm seeing that build with tag 124 (and latest) is being pushed continuously to Docker hub.
I am assuming there's a problem in the build process because I checked the repo and noticed that chromium 133 would be available.

Is there anything else I can check or do to help resolving the issue?

[andreyfel]

See details in: #254