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 eslint-plugin-node is breaking the build 🚨 #99

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 5.2.0 of eslint-plugin-node just got published.

Branch Build failing 🚨
Dependency eslint-plugin-node
Current Version 5.1.1
Type devDependency

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

As eslint-plugin-node 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 :muscle:

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/280859653?utm_source=github_status&utm_medium=notification)
Release Notes v5.2.0

Bug fixes

Commits

The new version differs by 5 commits.

  • 7189722 5.2.0
  • e7878e9 Update: fix missing deprecated APIs in v6 (fixes #92)
  • 52ceb11 Chore: rm superfluous argument. (#93)
  • 69dc50a Chore: update .travis.yml
  • effdd10 Fix: fix tests for linter.reset

See the full diff

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

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