This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of protractor.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 254 commits .
f79cec8chore(release): Version bump and changelog for 4.0.13
c3978ecfix(revert): element(locator).then should not appear in the docs and change reverted. (#3808)
81a6eaadocs(element): fix docs for element(locator).then
7f443c7chore(release): Version bump and changelog for 4.0.12
50c29acchore(scripts): clean up package scripts (#3794)
4449112chore(cleanup): jshint cleanup for spec (#3800)
742f264fix(driverProviders): quit forked instances w/ local driver provider (#3787)
7d481d6fix(ExpectedConditions): non-static ExpectedConditions for browser (#3766)
12c5139docs(website): improve docs for $ and $$ (#3773)
6193728chore(tests): Testapp with @angular/upgrade/static (ngUpgrade for AoT apps) (#3758)
19f99d6chore(browser): fix typings for getCapabilities (#3742)
Hello lovely humans,
protractor just published its new version 4.0.13.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of protractor. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 254 commits .
f79cec8chore(release): Version bump and changelog for 4.0.13c3978ecfix(revert): element(locator).then should not appear in the docs and change reverted. (#3808)81a6eaadocs(element): fix docs for element(locator).then7f443c7chore(release): Version bump and changelog for 4.0.1250c29acchore(scripts): clean up package scripts (#3794)4449112chore(cleanup): jshint cleanup for spec (#3800)742f264fix(driverProviders): quit forked instances w/ local driver provider (#3787)7d481d6fix(ExpectedConditions): non-static ExpectedConditions for browser (#3766)12c5139docs(website): improve docs for $ and $$ (#3773)6193728chore(tests): Testapp with@angular/upgrade/static(ngUpgrade for AoT apps) (#3758)19f99d6chore(browser): fix typings for getCapabilities (#3742)70bc6eachore(refactor): preferpath.resolve(#3751)40eb493chore(docs): update docs to use webdriver-manager for mobile setup (#3320)f773f5fchore(testapp): upgrade angular 2 versions (#3746)9fdd3d3chore(npm): add some artifacts to npmignore (#3747)There are 250 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade