search

webdriverio-boneyard / wdio-sync

A WebdriverIO v4 plugin. Helper module to run WebdriverIO commands synchronously.
http://v4.webdriver.io
MIT License
17 stars 31 forks source link

An in-range update of npm-run-all is breaking the build 🚨 #117

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 4.1.2 of npm-run-all was just published.

Branch Build failing 🚨
Dependency npm-run-all
Current Version 4.1.1
Type devDependency

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

npm-run-all 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](https://travis-ci.org/webdriverio/wdio-sync/builds/298512356?utm_source=github_status&utm_medium=notification)
Release Notes v4.1.2

Bug fixes

  • 096779b fixed the problem that --aggregate-output option does not work if child tasks print large output (#111). Thank you, @jlopezxs!
  • 693261b fixed the problem that --aggregate-output option does not work on npm-run-all command.
  • 528d105...43a6b16 fixed the problem with using yarn (#113).
Commits

The new version differs by 8 commits.

  • ec4d56c 4.1.2
  • cc8611c Chore: upgrade dependencies
  • 43a6b16 Chore: fix tests
  • dfb9dcb Fix: fix for latest yarn
  • 528d105 Chore: trivial fix
  • 693261b Fix: missing --aggregate-output in npm-run-all
  • 096779b Fix: --aggregate-output cannot handle large data (fixes #111)(#112)
  • 6ef64ab Chore: add Node 9 to Travis CI

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 6 years ago

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