An in-range update of grunt is breaking the build π¨
Opened this issue Β· 2 comments
The devDependency grunt was updated from 1.0.3
to 1.0.4
.
π¨ View failing branch.
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 could not complete due to an error (Details).
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
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.3 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 from1.0.4
to1.1.0
.
Your tests are still failing with this version. Compare changes
Release Notes for v1.1.0
- Update to mkdirp ~1.0.3
- Only support versions of Node >= 8
Commits
The new version differs by 8 commits.
d5cdac0
Merge pull request #1706 from gruntjs/tag-neew
4674c59
v1.1.0
6124409
Merge pull request #1705 from gruntjs/mkdirp-update
0a66968
Fix up Buffer usage
4bfa98e
Support versions of node >= 8
f1898eb
Update to mkdirp ~1.0.3
75da17b
HTTPS link to gruntjs.com (#1683)
6795d31
Update js-yaml dependecy to ~3.13.1 (#1680)
See the full diff