babel-cli@6.14.0 breaks build 🚨 #166

Closed

greenkeeperio-bot wants to merge 1 commit from greenkeeper-babel-cli-6.14.0 into master

greenkeeperio-bot commented

2016-09-28 20:20:37 +00:00

(Migrated from github.com)

Hello lovely humans,

babel-cli just published its new version 6.14.0.

State	Failing tests 🚨
Dependency	babel-cli
New version	6.14.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build went from success to failure.

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 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}

Hello lovely humans, [babel-cli](https://www.npmjs.com/package/babel-cli) just published its new version 6.14.0. <table> <tr> <th align=left> State </th> <td> Failing tests :rotating_light: </td> </tr> <tr> <th align=left> Dependency </td> <td> babel-cli </td> </tr> <tr> <th align=left> New version </td> <td> 6.14.0 </td> </tr> <tr> <th align=left> Type </td> <td> devDependency </td> </tr> </table> This version is **covered** by your **current version range** and after updating it in your project **the build went from success to failure**. 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: Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on. Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and while I’m just a bot, there is a group of people who are happy to teach me new things. [Let them know](https://github.com/greenkeeperio/greenkeeper/issues/new). Good luck with your project :sparkles: You rock! :palm_tree: --- This pull request was created by [greenkeeper.io](https://greenkeeper.io/). <sub>Tired of seeing this sponsor message? :zap: `greenkeeper upgrade`</sub>