Skip to content

Conversation

@greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

package-config-checker just published its new version 1.0.1.

State Failing tests ⚠️
Dependency package-config-checker
New version 1.0.1
Type devDependency

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

It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.

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!

🌴


The new version differs by 7 commits .

  • a7d607e Release v1.0.1
  • 1c80159 Use realPath instead of path to try to fix #2
  • 0a6792c Update dependencies
  • 996d1d6 Use extracted colour functions
  • 3a79c1c Add missing command to README example
  • ecebc61 Add a worked example to README
  • fe500f4 Add npm badge to README

See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@coveralls
Copy link

coveralls commented Jul 21, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling 55a0412 on greenkeeper-package-config-checker-1.0.1 into a476baf on master.

@Scrum Scrum merged commit 870f6d8 into master Jul 22, 2016
@Scrum Scrum deleted the greenkeeper-package-config-checker-1.0.1 branch July 22, 2016 22:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants