Closed taraspos closed 3 years ago
Upon new release, docker image with-chromedriver got released with updated chromedrvier version and old chrome version:
with-chromedriver
This results in the broken 86-with-chromedriver tag (86-with-selenoid as well), because 89 chromedriver doesn't work with 86 chrome.
86-with-chromedriver
86-with-selenoid
89
86
Any way to prevent building such an image?
Upon new release, docker image
with-chromedrivergot released with updated chromedrvier version and old chrome version:This results in the broken
86-with-chromedrivertag (86-with-selenoidas well), because89chromedriver doesn't work with86chrome.Any way to prevent building such an image?