Closed greenkeeper[bot] closed 5 years ago
Merging #273 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #273 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 4 4
Lines 77 77
=====================================
Hits 77 77
Continue to review full report at Codecov.
Legend - Click here to learn more
Ξ = absolute <relative> (impact)
,ΓΈ = not affected
,? = missing data
Powered by Codecov. Last update 20f650d...ab12ff7. Read the comment docs.
Update to this version instead π
The new version differs by 8 commits.
ec4d56c
4.1.2
cc8611c
Chore: upgrade dependencies
43a6b16
Chore: fix tests
dfb9dcb
Fix: fix for latest yarn
528d105
Chore: trivial fix
693261b
Fix: missing --aggregate-output in npm-run-all
096779b
Fix: --aggregate-output
cannot handle large data (fixes #111)(#112)
6ef64ab
Chore: add Node 9 to Travis CI
See the full diff
Update to this version instead π
The new version differs by 6 commits.
52eaf86
4.1.3
61bad5c
Chore: upgrade dependencies
35f86ae
Fix: unexpected behavior of leading bang (#124)
c76db0e
Docs: typo fix in README.md: is/are (#120)
d56c268
Fix: colorize tasks names sequentially instead of by hash (#115)
21c0269
Chore: trivial fix
See the full diff
devDependency
npm-run-all was updated from 4.0.2
to 4.1.4
.devDependency
npm-run-all was updated from 4.0.2
to 4.1.5
.
Version 4.1.0 of npm-run-all just got published.
The version 4.1.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 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.
Release Notes
v4.1.0Features
--aggregate-output
option. This option avoids that the output of tasks is mixed even if parallel mode. Don't use this option if the task never finishes such as web server.Thank you, @fatso83 !
Bug fixes
npm-run-all
showsMaxListenersExceededWarning
warnings if it runs many tasks in parallel.Commits
The new version differs by 14 commits.
59219e8
4.1.0
f7f7b43
Fix: MaxListenersExceededWarning (fixes #105)
64f6479
Chore: use async/await in tests
66fa8ff
Chore: upgrade dependencies
8c8bec0
Docs: update docs
8c6debf
Chore: tweak CI settings
5fcc2c6
Chore: no package-lock
e07e782
New: add
--aggregate-output
option (fixes #36)(#104)dff6409
Docs: add note about Yarn compatibility (#103)
94f1b64
Merge pull request #101 from ntwb/patch-1
a8364ce
Add Node.j 8.x to AppVeyor CI
c6d3092
Add Node.js 8.x to Travis CI
873f036
Merge pull request #95 from goto-bus-stop/feature/docs-in-pkg
0fca0e0
Include docs in published npm package.
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: