An in-range update of grunt is breaking the build 🚨

[greenkeeper]

Version 1.0.2 of grunt was just published.

Branch	Build failing 🚨
Dependency	grunt
Current Version	1.0.1
Type	devDependency

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

grunt is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

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

---

Commits

The new version differs by 27 commits.

• ccc3163 v1.0.2
• e7795dc Remove iojs from test matrix (#1622)
• a6a133b Remove deprecation warning for coffeescript (#1621) r=@vladikoff
• 06b377e https links to webchat.freenode.net and gruntjs.com (#1610)
• 7c5242f Use node executable for local grunt bin for Windows support
• f6cbb63 Oh right, Windows isnt bash
• a9a20da Try and debug why appveyor is failing on npm
• 48bba6c Move to the test script to avoid npm was unexpected at this time.
• 6b97ac0 Try to fix appveyor script
• 19003ba For appveyor, check node version to decide whether to install npm@3
• 3fcf921 Install npm@3 if npm version is npm 1 or 2
• 77fc157 Use the local version of grunt to run tests
• 400601a Updating devDependencies
• 6592ad1 Update travis/appveyor to node versions we support
• b63aeec Dont manually install npm, use the version each node version corresponds with

There are 27 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 1.0.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.