Updates adm-zip
to version 0.5.2
.
Fixes for macOS ChromeDriver download. If you are using a macOS and are
running into a WebDriver.createSession
error, run
webdriver-manager clean
to remove the downloaded ChromeDriver
before running webdriver-manager update
.
(4f5f736) fix(chromedriver): get most recent version on x64 windows if multiple major versions exist (#473)
(17db8a2) fix(binaries): filter m1 mac chromedriver versions (#478)
Updates to Chromedriver to the LATEST_RELEASE. This should work from here on in when Chrome is updated to a new version.
64795b7 chore(chrome) get latest chromedriver from LATEST_RELEASE (#418)
Update the max Chrome version to 76.
Update the max Chrome version to 75.
Fixes issues introduced by 12.1.3 (--versions.chrome flag and status command did not work). Also prevents downloading version 75 using the config.json file.
(0a6ce24) fix(chromedriver): version fixes for update, status, and start (#380)
Fixes download issues for chromedriver version 74+.
Versions of Chromdriver were versioned as 2.xx. We previously used to tack on a '.0' at the end to make it a semver version. This is why it was not downloading 74.0.3729.6. We now have to change 74.0.3729.6 to be a semver. We will do this by grabbing 74.0.3729 with a regex.
This should work when downloading the latest chromedriver version since
2.46.0 < 74.0.3729. If Chromedriver releases 75 but we are still on
Chrome 74, this will still break in this version of webdriver-manager.
This does not prevent latest Chromedriver and latest Chrome mismatches.
If you run into an issue where Chromedriver is mismatched with Chrome,
use the --versions.chrome
flag to pass in the version to download.
Fixes download issues for the selenium jar file.
This fix is here because selenium now has .zip files in the .xml. This worked previously since there were no .zip files and it would find a version that matched the latest jar file.
Also do not download alpha versions since we are also not downloading beta versions of the jar file.
closes #370
(f17b226) Fix(types): Operator '==' cannot be applied to types 'string | string[]' and 'number' (#297)
(7dbc1df) fix(clean): remove existing chrome meta files from update on clean command (#279)
(0a4c065) fix(appium): change appiumPort to seleniumPort for selenium server request (#228)
(6775421) deps(package): update npm audit.
npm audit fix --force
.closes #314
closes #207.
closes #221
the user. Also, API limit is reached, the error message now directly informs when any other failure occurs the status code is reported. This should hopefully give more info for issue #216.
This release gets the latest release for selenium standalone, chromedriver, iedriver, and gecko driver by downloading and parsing either a json or xml file. These json or xml files are cached in the selenium directory. This means for users that provide an alternative cdn will also be required to provide the proper xml or json server response to find these binaries.
Since we are always downloading the latest, the config.json
versions will no
longer be a place to override these.
If a new release is out and you have old binaries, running webdriver-manager
start
without specifying any versions should throw an error. The error will
tell the user that the binary is not present.
Since we are downloading the latest and not maintaining a default version in
config.json
, we are dropping the default tag.
This reads the xml from the CDN to get the latest chromedriver, iedriver, or standalone version if the version is 'latest'. If the release is from Github, use the Github API to get the releases. Also store the downloaded information to a cache in the output directory (default: selenium/). If the file is older than one hour it will be rewritten.
When getting the status, we are no longer showing the default version. Default versions will be deprecated and will be removed from the config.json file.
When starting the standalone server, use the 'latest' version by default unless specified by --versions.{binary} flag.
Change the gulp update task to use 3.0.0-beta4 so Firefox tests will pass.
closes #180
Also bump the geckodriver version to latest.
(72e3d9f) feat(status): show the last downloaded version when using status (#177)
closes #172
(a3b46c7) fix(iedriver): if downloading x64, use x64 version on start command (#173)
closes #147
(b5638ef) feat(update): on update, write full binary paths to file (#140)
Adding back in curl calls, these were removed on the new
Downloader.getFile
. Add curl call to reflect proxies.
Fix output dir to read from update's options instead of Config
Feature will help directConnect users for Protractor. The file will keep track of the last binary version as well as all other binaries downloaded.
The file will be created in the output directory. By default this is
selenium/update-config.json
. On clean
this file will be removed.
webdriver-manager update --versions.chrome=2.20 --standalone=false
--gecko=false
file created:
{
"chrome": {
"last": "/opt/src/webdriver-manager/selenium/chromedriver_2.20",
"all": ["/opt/src/webdriver-manager/selenium/chromedriver_2.20"]
}
}
then the user wants to use 2.25:
webdriver-manager update --versions.chrome=2.25 --standalone=false
--gecko=false
file created:
{
"chrome": {
"last": "/opt/src/webdriver-manager/selenium/chromedriver_2.25",
"all": ["/opt/src/webdriver-manager/selenium/chromedriver_2.20",
"/opt/src/webdriver-manager/selenium/chromedriver_2.25"]
}
}
The default was x86-64, but x86 cannot be emulated on ARM. This makes more sense
When scripting, you might want to defensively run a shutdown
command. If the shutdown fails
because the server is already off, you don't care. If it fails for another reason, you do care.
So I made trying to shutdown a server which is already off just a warning. I added a flag in case
you want the old behavior though.
--quiet
and --verbose
flags to control the level of output (#156)I added the --quiet
flag for cases like:
where currently the start --detach; ./tests.sh; webdriver-manager shutdown
selenium server output will get mixed in with other output.
I also added the
--verboseflag for
webdriver-manager updatein case you *really* wanted to
see all the output which gets eaten by using
--android-accept-licenses`.
Closes https://github.com/angular/webdriver-manager/issues/51
Before, we were just waiting for the emulator to be running, rather than waiting for the OS to be
booted up and ready to instance chrome.
While I was doing that I moved some stuff into lib/utils.ts
since I felt like too much of
lib/cmds/start.ts
was being devoted to this one feature.
Also closes https://github.com/angular/webdriver-manager/issues/166
2a1505f
broke androidOtherwise we’ll won’t terminate until the whole file was downloaded, even though we don’t need it.
(c16bf90) chore(es6): allow to use es6 promises (#160)
(1f9713a)
feat(start and shutdown): Added --detach
option for start
command and new shutdown
command
(#130)
(88cf46b) feat(version): have a way to get the package version (#136)
closes #119
(5966b6a) fix(cli): fix setting flag to false (#135)
webdriver-manager update --gecko=false
webdriver-manager update --gecko=0
. Minimist interprets 0 as true.(35676ee) fix(gecko): follow redirects for content-length (#133)
(dc2f9f9) fix(cli): fix default option values, boolean and string handling (#110) (#122)
minimist
(88d6105) fix(gecko): Update geckodriver to 0.11.0 and fix suffixes. (#128)
Fixes #111
(707e015) fix(android): fixed four things for android: (#116)
google_apis
closes #107
closes #106
(3984ea4) fix(filemanager): respect proxy/ignoreSSL options in contentLength HEAD request (#101)
(946ee00) fix(chrome_driver): use the x64 binary if chrome driver version is greater than 2.23 (#95)
closes #93
closes #96
Chromedriver < 2.24 has issues with Chrome 54+ (https://bugs.chromium.org/p/chromedriver/issues/detail?id=1451).
Users will still need 'marionette': true in their capabilities in order to use gecko driver.
closes #68
closes #79
closes #60
closes #68
closes #61
upgrade to latest chrome driver and selenium standalone server versions
closes #53
closes #55
(d3724fb) fix(config): simplify locating configuration file, selenium folder (#41)
closes #32
(70d32df) fix(dir): check selenium dir and warn user that the folder does not exist (#17)
(0ec1443) fix(binary): file type, unzipping, and permissions
closes #20
closes #6
(c34b05c) fix(bin): local, project, and global usage
(4a0caf5) fix(dep): fix dependency for chalk
(15ae0e8) fix(chmod): set permissions to 755
(1820fbc) Initial commit
closes #8
closes #5
closes #11