An in-range update of sake-outdated is breaking the build 🚨

[greenkeeper]

Version 0.1.28 of sake-outdated just got published.

Branch	Build failing 🚨
Dependency	sake-outdated
Current Version	0.1.27
Type	devDependency

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

As sake-outdated 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 6 commits.

• f47eeb0 0.1.28
• fcf457b Upgrade npm4-check-updates for Node 8 fixes
• 6367fce Update sake-bundle, sake-cli
• 9f5efb2 Update coffee-script
• a329992 Update sake-bundle
• 44663e3 Update sake-cli, sake-publish

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴