search

issuemd / issue.md

issuemd website development repo
https://issue.md
MIT License
0 stars 0 forks source link

An in-range update of babel-cli is breaking the build 🚨 #34

Open greenkeeper[bot] opened 7 years ago

greenkeeper[bot] commented 7 years ago

Version 6.26.0 of babel-cli just got published.

Branch Build failing 🚨
Dependency babel-cli
Current Version 6.24.1
Type devDependency

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

As babel-cli 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 - ❌ **bitHound - Dependencies** 1 failing dependency. [Details](https://www.bithound.io/github/issuemd/issue.md/10f4676c38b6d2ab2762bd033db7cb023738c27d/dependencies/npm#filter-failing-dep) - ❌ **bitHound - Code** 2 failing files. [Details](https://www.bithound.io/github/issuemd/issue.md/10f4676c38b6d2ab2762bd033db7cb023738c27d/files#filter-failing-file) - ✅ **ci/circleci** Your tests passed on CircleCI! [Details](https://circleci.com/gh/issuemd/issue.md/127?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
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 6.24.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.