An in-range update of protractor is breaking the build π¨
greenkeeper opened this issue Β· comments
Version 5.2.1 of protractor was just published.
Branch | Build failing π¨ |
---|---|
Dependency | protractor |
Current Version | 5.2.0 |
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 15 commits.
7bf873b
chore(release): bump version number (#4599) (#4618)
3b29ee7
fix(doc): update links in debugging docs to make it show correctly in the website (#4615)
18d06e8
chore(release): bump version number (#4599)
e51f0ec
fix(doc): update doc for testing with node 8 async/await and chrome inspector. (#4613)
5d13b00
fix(jasmine): Update Jasmine to support Node8 async/await (#4608)
1b486a2
docs(readme) add link to DEVELOPER.md (#4596)
8d71a1b
docs(page-objects.md): Refactor the existing Page Object example (#4576)
a62efc6
feat(locators): Add support for regex in cssContainingText (#4532)
95dd3ca
doc(tutorial): added example for element.getAttribute('value') to read text from an input (#4566)
1aaf1c1
Corrected the formatting of a code sample (#4561)
b204a83
doc(browser-support) improved Firefox documentation (#4553)
8ac0f47
Add docs for debugging with the control flow disabled (#4555)
b20fce2
Corrected the path to Protractor cli.js (#4560)
60d5d90
Update clientsidescripts.js (#4544)
bb63ab0
Update to the latest blocking proxy (#4546)
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 π΄
After pinning to 5.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 5.2.2 just got published.
Your tests are still failing with this version. Compare the changes π¨
Commits
The new version differs by 3 commits.
b43081f
chore(release): version bump and changelog for 5.2.2 (#4626)
a5125de
Revert "fix(jasmine): Update Jasmine to support Node8 async/await (#4608)" (#4625)
8e5ad1f
fix(doc): remove unnecessary config in debugging doc/example (#4622)
See the full diff