Open greenkeeper[bot] opened 6 years ago
devDependency
concurrently was updated from 3.6.1
to 4.1.0
.Update to this version instead π
The new version differs by 8 commits.
313de53
4.1.0
13b20fd
docs: clarify successCondition (#176)
3173b36
Add support for yarn (#171)
e24a025
Update CONTRIBUTING.md (#172)
5a1f56f
npm: update rxjs to ^6.3.3 (#170)
a96b9cf
Test streams returned by flow controllers
4b5bfa3
bin: fix version command
455ed3e
ci: report coverage results to Coveralls after success
See the full diff
devDependency
concurrently was updated from 3.6.1
to 4.1.1
.Update to this version instead π
--prefix-length
argument through (#189)devDependency
concurrently was updated from 3.6.1
to 4.1.2
.devDependency
concurrently was updated from 3.6.1
to 5.0.0
.devDependency
concurrently was updated from 3.6.1
to 5.0.1
.devDependency
concurrently was updated from 3.6.1
to 5.0.2
.devDependency
concurrently was updated from 3.6.1
to 5.1.0
.devDependency
concurrently was updated from 3.6.1
to 5.2.0
.
Version 4.0.0 of concurrently was just published.
The version 4.0.0 is not covered by your current version range.
If you donβt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of concurrently.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donβt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v4.0.0More than anything, v4 is just a big refactor to allow changes to be made faster and more reliably.
It does feature some small breaking changes, and maybe even fixes some longstanding bugs.
Breaking changes
--allow-restarts
is no more.Instead, just set
--restart-tries
to something greater than0
.--handle-input
flag. (#147)It does come with some specific input parsing that would make it difficult for you to use it.
none
will now actually not prefix commands' outputs.Previously, it would prefix with
[]
.SIGINT
s/Ctrl+C will now be handled gracefully. (#150)No more exiting with code
1
or tweaking--success
flag.No more
null
exit codes (#133)That's a pretty bad bug that existed till now. You won't see a log like this anymore:
What you will see going forward is the actual exit signal:
concurrently finally gets a shiny⨠programmatic API!
Closes #101, #112. Maybe even #103.
Check the docs here for some info on how to use it.
Commits
The new version differs by 28 commits.
3690676
4.0.0
b4e414c
npm: update and remove some deps
4043fc2
Exit gracefully on SIGINT (#164)
b1daf8d
logger: show no prefix when the format is none
58d7d97
Take options such as prefixLength and outputStream
1d0598a
docs: add programmatic API usage
571671b
Add missing export of LogExit
7ac9b6e
Remove unused RxJS schedulers
caa23b3
bin: change tested exit code to 1 on Windows (#163)
bfd7501
ci: run AppVeyor on Node 10
adcc0b5
Merge pull request #157 from kimmobrunfeldt/v4
0e60d2d
docs: move the why section to the top
b136183
docs: update help section
c127d92
Add support for prefix length (#162)
daddad1
bin: don't check order of lines emitted
There are 28 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donβt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: