bergie/hallo

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

greenkeeper opened this issue Β· 2 comments

Version 1.0.3 of 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

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. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

  • The devDependency grunt was updated from 1.0.3 to 1.0.4.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 5 commits.

  • 8fcbed1 v1.0.4 (#1668)
  • 0b13970 Update js-yaml to address https://npmjs.com/advisories/788 (#1667)
  • 7db6cf7 Use SOURCE_DATE_EPOCH to render dates in template. (#1596)
  • a2d6d80 Revert "Indicate in package.json that Node.js 4 or newer is required (#1643)" (#1644)
  • 773b7e7 Indicate in package.json that Node.js 4 or newer is required (#1643)

See the full diff