An in-range update of protractor is breaking the build 🚨

[greenkeeper]

Version 4.0.14 of protractor just got published.

Branch	Build failing 🚨
Dependency	protractor
Current Version	4.0.13
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As protractor is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 17 commits .

• 8952eab chore(release): Version bump and changelog for 4.0.14
• 688f5d6 deps(update): update vrsource-tslint-rules and webdriver-manager (#3856)
• c437fd3 deps(selenium-webdriver): clean up types selenium-webdriver (#3854)
• 989759a chore(tslint): add tslint to gulpfile (#3833)
• 075a512 chore(error): improve error message for local and direct driver providers (#3850)
• 83694f5 fix(types): update for selenium-webdriver types creating transpile errors (#3848)
• 41b5a19 chore(docs): add test app link to issue template (#3843)
• ea09be4 fix(jasmine): Return the full test name in Jasmine test results. (#3842)
• c9fad62 tests(element): We can now pass elements to executeScript. (#3844)
• 2e6c1be docs(locators): add $$ shortcut to locators.md (#3845)
• 2a8c252 chore(docs): fixes grammar issue in page title (#3821)
• 2cf2453 chore(repo): organize ignore files (#3841)
• 76cb4b4 fix(element): Fix typing of then function (#3785)
• 5a12d69 fix(config): cucumberOpts.require should be an optional Array of strings (#3817)
• b337a8e feat(config): add seleniumServerStartTimeout (#3791)

There are 17 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 4.0.13 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.