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 🚨 #49

Closed
greenkeeper bot opened this issue Jun 29, 2017 · 2 comments
Closed

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jun 29, 2017

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 💪

Status Details
  • coverage/coveralls First build on greenkeeper/eslint-plugin-import-2.6.1 at 98.795% Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

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 and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jun 29, 2017

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.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jul 6, 2017

Version 2.7.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 7 commits.

  • c9dd91d bump to v2.7.0
  • ee5a986 changelog note for #843
  • 0dc4451 Merge branch 'no-absolute-path-perf'
  • f70d127 upgraded no-absolute-path to use moduleVisitor pattern to support all module systems
  • e4b8884 PR note fixes
  • 5aa2fe0 Rename funtion reportIfMissing to reportIfAbsolute
  • 3e8438e Extract isAbsolutePath from importTypes helper

See the full diff

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

No branches or pull requests

1 participant