Skip to content
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

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

Open
greenkeeper bot opened this issue Dec 25, 2018 · 1 comment
Open

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

greenkeeper bot opened this issue Dec 25, 2018 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Dec 25, 2018

The devDependency protractor was updated from 5.4.1 to 5.4.2.

🚨 View failing branch.

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 could not complete due to an error (Details).

Commits

The new version differs by 7 commits ahead by 7, behind by 1.

  • 5d29112 chore(release): bump version to 5.4.2 (#5106)
  • db1b638 feat(saucelabs): add sauceRegion support for eu datacenters (#5083)
  • 3a5e413 chore(config): Update docs regarding proxies (#5048)
  • 6064b69 chore(tests): clean up test suite for failures (#5097)
  • f5dbe13 fix(deps): @types/node is now a dev dependency
  • d4fe1ca chore(config): Update sauceSeleniumAddress port to 443 (#5041)
  • 71e2cb8 chore(release): version bump and changelog for 5.4.1. (#4953)

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 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Dec 25, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants