Giters

paperhive / frontend

PaperHive frontend

Home Page:https://paperhive.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

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

greenkeeper opened this issue · comments

commented

Version 5.2.0 of protractor was just published.

Branch Build failing 🚨
Dependency protractor
Current Version 5.1.2
Type devDependency

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

protractor is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

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

The new version differs by 20 commits.

  • c2cf0db chore(release): version changelog for 5.2.0
  • 0fbc2c0 chore(release): update selenium-webdriverjs and bump version number (#4538)
  • 862e8be fix(circleci): Disable testcases for "useBlockingProxy" (#4523)
  • f7e17f3 fix(clientSideScripts): change protractor to support waiting for hybrid app (#4512)
  • 15776b8 Export Locator (#4459)
  • 6be98ea docs(plugins): fix links and formatting (#4431)
  • 4b7cada fix(sauce): bring back sauceProxy as a configuration option (#4419)
  • b87159b fix(website): fix all locator examples to use element over browser.findElement (#4413)
  • 768fd39 fix(local): allow local driver provider to use gecko driver from config (#4412)
  • c0b8770 docs(website): fix issue 4246
  • f79938e docs(plugins): add ng-apimock plugin to plugins.md
  • ab1afb0 fix(blockingproxy): Start bpRunner strictly after setupDriverEnv
  • b85e7ee fix(npmignore): .map files in built directory cause stacktrace lines to nowhere
  • 299fc8d docs(browser-support): Fixed incorrect example
  • e5a5d59 docs(frameworks) align cucumberOpts comments

There are 20 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

commented

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