gucong3000/safetree

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

greenkeeper opened this issue · 1 comments

greenkeeper commented

Version 2.9.0 of eslint-plugin-import was just published.

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

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

eslint-plugin-import 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/appveyor/branch AppVeyor build succeeded Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Commits

The new version differs by 101 commits.

  • 180d71a bump plugin to v2.9.0
  • 0231c78 Merge pull request #1026 from isiahmeadows/patch-1
  • ae5a031 Missed a link
  • 5b0777d Add no-default-export + docs/tests (#936)
  • ff3d883 Merge pull request #1025 from patrick-steele-idem/update-dependencies
  • 654d284 Merge pull request #1024 from patrick-steele-idem/issue-1023
  • 9b20a78 Upgraded "find-root" and "lodash.get" for the webpack resolver
  • 8778d7c Fixes #1023 - Load exceptions in user resolvers are not reported
  • 91cfd6d Merge pull request #1022 from nevir/patch-1
  • 0e729c7 no-self-import is unreleased
  • 219a8d2 Merge pull request #1012 from silvenon/extensions-export
  • ab49972 Support export declarations in extensions rule
  • 3268a82 Merge pull request #1010 from silvenon/extensions
  • fdcd4d9 Add a .coffee test proving extension resolve order
  • bc50394 Merge pull request #1009 from silvenon/extensions

There are 101 commits in total.

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 commented

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