We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
latest
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I do docker pull selenium/standalone-chrome-debug, I should get the latest release, right now is 3.4.0-dysprosium.
docker pull selenium/standalone-chrome-debug
Right now I am getting a release done 2 months ago. This is because the latest is pointing to the wrong image. Check https://hub.docker.com/r/selenium/standalone-chrome-debug/tags/
I think we made a mistake in the most recent release. I will check the other images to see if this is also happening there.
The text was updated successfully, but these errors were encountered:
Also happening on: https://hub.docker.com/r/selenium/node-phantomjs/tags/ https://hub.docker.com/r/selenium/base/tags/ https://hub.docker.com/r/selenium/standalone-firefox-debug/tags/
Sorry, something went wrong.
this should be fixed from https://github.com/SeleniumHQ/docker-selenium/releases/tag/3.4.0-einsteinium.
let's wait and see. we'll leave this issue open until validated.
Yeah, I checked and the tag is well placed in all the images. Thanks!
No branches or pull requests
Expected Behavior -
When I do
docker pull selenium/standalone-chrome-debug
, I should get the latest release, right now is 3.4.0-dysprosium.Actual Behavior -
Right now I am getting a release done 2 months ago. This is because the
latest
is pointing to the wrong image.Check https://hub.docker.com/r/selenium/standalone-chrome-debug/tags/
I think we made a mistake in the most recent release. I will check the other images to see if this is also happening there.
The text was updated successfully, but these errors were encountered: