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

[greenkeeper]

Version 1.3.0 of grunt-cli was just published.

Branch	Build failing 🚨
Dependency	grunt-cli
Current Version	1.2.0
Type	devDependency

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

grunt-cli 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 11 commits.

• 89ab5d7 Merge pull request #120 from gruntjs/tag-1.3.0
• 28e8220 Fix node versions and CI
• ebd818b Release v1.3.0
• eaf78d6 Merge pull request #117 from gruntjs/liftoff
• 98ba9e6 Use ~ for deps and update v8flags to 3.0.2
• 8ae6299 Fix completions to use old Grunt style for now
• 0c5f397 Fix version and help with no gruntfile
• ea01dc5 Include grunt-cli version with --version
• 7b8cb3f Implement liftoff into grunt-cli
• 7f6298e Merge pull request #104 from paladox/patch-3
• ccb75a6 Update grunt to 1.0.1

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.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

Version 1.3.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 2 commits.

• 352a258 v1.3.1
• 89e264b cwd option should use existing base option (#122)

See the full diff