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 babel-plugin-istanbul is breaking the build 🚨 #28

Open
greenkeeper bot opened this issue Apr 7, 2018 · 1 comment
Open

Comments

@greenkeeper
Copy link

greenkeeper bot commented Apr 7, 2018

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.1.6 of babel-plugin-istanbul was just published.

Branch Build failing 🚨
Dependency babel-plugin-istanbul
Current Version 4.1.5
Type devDependency

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

babel-plugin-istanbul 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 is in progress Details
  • bitHound - Code No failing files. Details
  • bitHound - Dependencies 1 failing dependency. Details

Commits

The new version differs by 6 commits.

  • 321740f chore(release): 4.1.6
  • 77b6eb7 chore: explicit update of istanbul dependencies (#149)
  • 428a952 fix: include object-spread-syntax plugin (#141)
  • 18fe954 fix: babel-preset-es2015 => babel-preset-env (#138)
  • 7045a03 chore(package): update coveralls to version 3.0.0 (#133)
  • 38176ba chore(package): update mocha to version 4.0.0 (#134)

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
Author

greenkeeper bot commented Apr 7, 2018

After pinning to 4.1.5 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