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

## Version **1.0.3** of [grunt](https://github.com/gruntjs/grunt) was just published.

Branch


Build failing 🚨




Dependency


grunt




Current Version


1.0.2




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](https://travis-ci.org/kss-node/grunt-kss/builds/387574044?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 10 commits.

• 9ba3a99 1.0.3


• eee4c33 Changelog v1.0.3


• 46da7f2 Merge pull request #1636 from gruntjs/upt


• 00f4d8a Drop support for Node 0.10 and 0.12


• e852727 util update


• 56d702e Update deps


• 0105524 Fix race condition with file.mkdir and make it operate more similarily to mkdir -p (#1627) r=@vladikoff


• 303d445 https links (#1629)


• d969132 Merge pull request #1624 from gruntjs/rm-bump-deps


• 289ff91 Remove old bump task and deps

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Start with the linked Travis CI failure and compare the project's grunt 1.0.2 dependency with version 1.0.3, including the listed Node support change. Done means the Travis build passes with the intended grunt version, but the payload names no source file or test to guide the investigation.

Written by the indexing model from the issue text.