This version 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-exec.
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.
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.
6cb50e1#76 ability to specify a function for cwd. Also added maxbuffer verbose logging to ease troubleshooting
d605a80#75 Better error reporting during a maxBuffer exceeded (or any other error condition) as well as testing of larger maxBuffer sizes (just manual tests)
19a622cGruntfile changes for testing reported bugs
bed8ba6Merge pull request #74 from RobLoach/update
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
grunt-exec just published its new version 2.0.0.
This version 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-exec. 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.
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 26 commits .
e1ef5d9
2.0.0
82f5c2e
Added support for shortcut 'stdio', fix for 'ignore', potential fix for travis CI failures
36f7b55
switched test to use nodejs instead of assuming 'exit' shell command
ef888cb
Trying detached executions for 'exit' tests in Travis-CI, minor verbose message fix
0e54d44
Major change to child_process.spawn while simulating previous behavior
196d7ad
1.0.1
6cb50e1
#76 ability to specify a function for cwd. Also added maxbuffer verbose logging to ease troubleshooting
d605a80
#75 Better error reporting during a maxBuffer exceeded (or any other error condition) as well as testing of larger maxBuffer sizes (just manual tests)
19a622c
Gruntfile changes for testing reported bugs
bed8ba6
Merge pull request #74 from RobLoach/update
62ecf2c
Update version targeting
603d470
Added nifty NPM stats
a3a557e
Merge pull request #63 from shaine/master
c4ea3dc
Document new stdin feature
e28d1f2
Merge pull request #62 from lipsumar/master
There are 26 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.