The version 3.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of grunt-jsinspect.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notesjsinspect v0.12 and no more Node.js v4
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 3.0.0 of grunt-jsinspect just got published.
The version 3.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of grunt-jsinspect. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
jsinspect v0.12 and no more Node.js v4jsinspect
now at version0.12.6
#42fs.existsSync
#43jsinspect
upgradeCommits
The new version differs by 15 commits.
50d67e6
Going to release third major
04eaae3
:tophat: dependencies
8e00ceb
Merge pull request #44 from stefanjudis/42-migrate-to-recent-jsinspect
aef2258
Documenting options :see_no_evil:
3717edf
Drop Node.js v4 and start testing against v8
1e786d7
Not all options were passed to inspector not reporter
8ed950b
Changed properties for v0.10.0 and the rest simply followed
7dd4a1e
Merge pull request #43 from stefanjudis/no-more-fs-exists
87bd478
No more deprecated Node.js fs API method
784c7dd
2.0.0 coming right up
9ab6015
Seeing is believing :tophat: No more npm update at Travis #41
080058b
Dropping Node.js 0.10 and minimum :pig: is 4.2.0 #41
a3a1ab8
Minimum Node.js version 0.10, instead of 0.8. Also testing the lowest, LTS and the latest
fb1db14
:tophat: dependencies
1eac0fb
Start to use Grunt.js v1.0.1 for development and unify version range strings
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: