Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
greenkeeper bot opened this issue Jun 24, 2019 · 1 comment
Open

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jun 24, 2019

The devDependency eslint-plugin-import was updated from 2.17.3 to 2.18.0.

🚨 View failing branch.

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/travis-ci/push: The Travis CI build failed (Details).
  • Travis CI - Branch: The build failed.

Commits

The new version differs by 26 commits.

  • c924f5d Bump to v2.18.0
  • c8132f2 Merge pull request #1393 from sheepsteak/eslint-6
  • 7e41d29 Make testVersion take a function to delay running require.resolve
  • d7023f6 Remove ESLint 6 from allowed failures in Travis
  • 3bee716 Use eslint@6 instead of eslint@6.0.0-alpha in Travis
  • d9b7258 Only run tests using typescript-eslint-parser on eslint@<6
  • c2b19d0 Update to @typescript-eslint/parser canary
  • 2f1f4da Allow ESLint@6
  • e6ea127 Use require.resolve when passing parser to RuleTester
  • 1029b4f Add ecmaVersion when required
  • b5ff64e Transform output of FileEnumerator into what rule expects
  • fc65509 Merge pull request #1389 from fooloomanzoo/patch-1
  • 4140870 Update no-named-as-default-member.md
  • 58b41c2 Merge pull request #1383 from golopot/node-12
  • 8974346 [Build] make node 12 pass CI

There are 26 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
Copy link
Contributor Author

greenkeeper bot commented Jun 24, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants