This version is covered by your current version range and after updating it in your project the build went from success to failure.
As time-grunt is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Coverage remained the same at 83.03% when pulling 4451916ed9c86d13b4f554015d37b4502771e413 on greenkeeper-time-grunt-1.4.0 into aa2859f69553fea1c1e70f4a7165347ca58c9c83 on master.
Coverage remained the same at 83.03% when pulling 05b830eb50596f336a5c57b28c1c8173023483eb on greenkeeper-time-grunt-1.4.0 into 3fafea49bddb421e901b1a03eccf208c52207b38 on master.
Coverage remained the same at 83.03% when pulling 9a3475ecd6df11df6b4dea01dd65173d0ceb5bc0 on greenkeeper-time-grunt-1.4.0 into c1884ae4e9a5f78613502143f825adfd224e0061 on master.
Coverage remained the same at 83.03% when pulling 9a3475ecd6df11df6b4dea01dd65173d0ceb5bc0 on greenkeeper-time-grunt-1.4.0 into c1884ae4e9a5f78613502143f825adfd224e0061 on master.
Coverage remained the same at 83.03% when pulling 5f9b6a5d70fae24d1ec6aeca3bf6727070abfa1b on greenkeeper-time-grunt-1.4.0 into 0d159fc4aecdcf130acef1cc930cf5b6eac02396 on master.
Coverage remained the same at 83.03% when pulling 2b99c007f9e7b4713bc09bb25d941b97c4e29804 on greenkeeper-time-grunt-1.4.0 into 6e981e2b74b90b0fb0264e102042a6f71b42ac39 on master.
Coverage remained the same at 83.03% when pulling c4b3a25c7380ff3a7c37cfa5f02a7e924a814dff on greenkeeper-time-grunt-1.4.0 into 86624498b55b0cd7b8df859fbfb59bc95c5b53ed on master.
Hello lovely humans,
time-grunt just published its new version 1.4.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As time-grunt is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 15 commits .
29dc47d
1.4.0
ce3b96f
update screenshot
9f42505
display local time instead of UTC time (#83)
3c67154
Override xo/no-process-exit
3ee8b23
Update .travis.yml
cbbabe0
Merge pull request #79 from sindresorhus/adrianlee44/fix-negative
d72863e
meta tweaks
2029b20
Merge pull request #75 from ntwb/patch-1
93a1d44
Travis CI: Test on Node.js v4.x.x and v5.x.x
db11c16
1.3.0
1472581
minor tweaks
e5b74e5
Close #73 PR: Ignore watch task. Fixes #51.
e16bf95
1.2.2
b42b4e7
Merge pull request #70 from dominykas/patch-1
efbee3a
Bumping pretty-ms to 2.x
See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade