search

webdriverio-boneyard / wdio-junit-reporter

A WebdriverIO v4 plugin. Report results in junit xml format.
http://v4.webdriver.io
MIT License
11 stars 42 forks source link

An in-range update of eslint-plugin-import is breaking the build 🚨 #66

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 2.6.1 of eslint-plugin-import just got published.

Branch Build failing 🚨
Dependency eslint-plugin-import
Current Version 2.6.0
Type devDependency

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

As eslint-plugin-import 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 failed [Details](https://travis-ci.org/webdriverio/wdio-junit-reporter/builds/248342325?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 4 commits.

  • d9b712a bump to v2.6.1 to bump dep on node resolver to latest 😳
  • 4d561e3 Merge pull request #881 from futpib/named-flow-import-interface
  • 56e60e4 Update no-extraneous-dependencies.md (#878)
  • 9a06426 Fix flow interface imports giving false-negative with named rule

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 2.6.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.