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 npm-run-all.
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.
b90575b fixed unintentional failing of the assertion check about --race option. If there is a mix of --parallel and --serial then --race option had failed always. (fixes #88).
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,
npm-run-all just published its new version 4.0.2.
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 npm-run-all. 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:
GitHub Release
Bug fixes
--race
option. If there is a mix of--parallel
and--serial
then--race
option had failed always. (fixes #88).The new version differs by 43 commits .
46cfd57
4.0.2
b90575b
Fix: it threw for --race even if --parallel exists (fixes #88)
acb1582
4.0.1
378c54b
Chore: switch to codecov
779720c
Chore: fix trivial
6beda60
Docs: update README.md
558da4b
Merge pull request #82 from vinkla/patch-1
181b689
Merge pull request #84 from bmarcaur/fix/npm-execpath-case-sensitivity
bb9e627
NPM_EXECPATH -> npm_execpath, this variable is case sensitive
81e3d0f
Merge pull request #83 from evilebottnawi/patch-2
b40fc7e
Fixed: typo in
help
CLI command.0190327
Simplify repository config
750f5d9
Docs: fix README.md
5e88fb7
4.0.0
12b2b87
Breaking: use NPM_EXECPATH to run tasks
There are 43 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.