[🐛 Bug]: Missing WebDriver Docker image 4.19.1 contrary to established conventions

What happened?

The WebDriver Docker Image for Selenium 4.19.1 is missing from Docker Hub.

This is contrary to standard conventions on which certain tools depend.

for example: Selenium 4.16.1 has published WebDriver Docker Images with tag 4.16.1 while Selenium 4.19.1 has not.

How can we reproduce the issue?

check https://hub.docker.com/r/selenium/standalone-chrome

Notice the presence of 4.16.1 tag and the absence of 4.19.1 tag

The same holds true for the whole WebDriver Docker Images group.

Relevant log output

Not directly relevant

Caused by: java.lang.RuntimeException: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=selenium/standalone-chrome:4.19.1, imagePullPolicy=DefaultPullPolicy(), imageNameSubstitutor=org.testcontainers.utility.ImageNameSubstitutor$LogWrappedImageNameSubstitutor@144ee8a7)
Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=selenium/standalone-chrome:4.19.1, imagePullPolicy=DefaultPullPolicy(), imageNameSubstitutor=org.testcontainers.utility.ImageNameSubstitutor$LogWrappedImageNameSubstitutor@144ee8a7)
Caused by: com.github.dockerjava.api.exception.NotFoundException: 
Status 404: {"message":"manifest for selenium/standalone-chrome:4.19.1 not found: manifest unknown: manifest unknown"}

Operating System

Linux

Selenium version

4.19.1

What are the browser(s) and version(s) where you see this issue?

Chrome

What are the browser driver(s) and version(s) where you see this issue?

4.19.1

Are you using Selenium Grid?

No response

Start by checking the selenium/standalone-chrome tags on Docker Hub and compare the missing 4.19.1 tag with the existing 4.16.1 convention. Then trace this repository’s WebDriver image publishing or release entry point; done means the 4.19.1 image tags are published across the WebDriver image group and can be pulled successfully.