-
Notifications
You must be signed in to change notification settings - Fork 116
downloaded chromedriver isn't the latest version #373
New issue
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
Comments
I would also like to know if webdriver-manager 12.1.1 will support chromedriver 73+ or if an update to 13.0.0 is required |
Redirect to full discussion here: angular/protractor#5225 I have backward compatibility support for Protractor 5.4.2 here: #372. From Protractor's point of view this isn't a major version bump BUT webdriver-manager 13 removes mobile support for appium and android sdk downloads so I'm not sure how to properly semver Protractor. Should this be 5.5? |
@cnishina I didn't get it...w-m is a standalone module, which can be downloaded and used separately from protractor, how its related to the fact it does not download latest chrome binaries? |
webdriver manager 13.0.0 works with latest naming of chrome drivers |
On npm there is 12.1.2, should I use webdriver-manager from a git release instead? |
I would hold off for now. I'm going to talk to Julie and Michael what we should do next. |
Now it's downloading the driver for chrome 75(chromedriver_75.0.3770.8.zip), which seems to be unreleased/beta channel. According this bug, we can't override to the correct version: bash-3.2$ webdriver-manager |
I just can't win today. I'm going to work on this tomorrow. Elevating this to P0. This needs to be fixed for 12. |
This has been fixed. See #376 |
Closing this issue. |
Hi guys. I'm doint
webdriver-manager update
and see that downloaded version of chromedriver on my macos is 2_46, whenever 73 and 74 already available - http://chromedriver.chromium.org/downloads, and it forces me to manually download latest binary and update it :(The text was updated successfully, but these errors were encountered: