Ran
|
Files
101
|
Run time
9s
|
Badge
Embed ▾
README BADGES
|
push
travis-ci
Auto merge of #6210 - ember-cli:greenkeeper-github-2.5.2, r=nathanhammond github@2.5.2 breaks build Hello lovely humans, [github](https://www.npmjs.com/package/github) just published its new version 2.5.2. <table> <tr> <th align=left> State </th> <td> Failing tests :rotating_light: </td> </tr> <tr> <th align=left> Dependency </td> <td> github </td> </tr> <tr> <th align=left> New version </td> <td> 2.5.2 </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 github 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: --- The new version differs by 7 commits . - [`dcbce76`](https://github.com/mikedeboer/node-github/commit/dcbce76a0) <code>bump to 2.5.2 and update changelog</code> - [`a9d1d94`](https://github.com/mikedeboer/node-github/commi... (continued)
3791 of 4115 relevant lines covered (92.13%)
556.36 hits per line
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|