Open greenkeeper[bot] opened 6 years ago
Update to this version instead ๐
Pushed to update the Readme that is displayed for npmjs.com to mention Node.js v6+ requirement for wait-on@3. Refers node.js v4 users to wait-on@2.1.2 and older engines to wait-on@1.5.4.
devDependency
wait-on was updated from 2.1.2
to 3.1.0
.devDependency
wait-on was updated from 2.1.2
to 3.2.0
.Update to this version instead ๐
Added --tcpTimeout option
--tcpTimeout
Maximum time in ms for tcp connect, default 300ms
thanks @Sarithis
devDependency
wait-on was updated from 2.1.2
to 3.3.0
.Update to this version instead ๐
The new version differs by 18 commits.
4192e0c
Merge remote-tracking branch 'origin/master'
e00b1a1
3.3.0
f3743de
Merge branch 'matijagaspar-master'
60296f1
mocha@6.1.4
bb28673
merge matijagaspar/master
fc766df
Merge pull request #36 from orarbel/patch-1
5c72236
add node 11 and 12 to travis config
3aa6068
removed node6 from supported node envs, joi@15 no longer supports it
34be295
update the require for joi
5b7313b
update joi package
c93fdd9
update package-lock.json
11ea59f
update joi, core-js, mocha and temp to newer versions
f1bfbe1
Update usage.txt
ee057ea
3.3.0-beta.0
1e8bb2c
Add --httpTimeout 123 in ms to HTTP HEAD/GET requests
There are 18 commits in total.
See the full diff
devDependency
wait-on was updated from 2.1.2
to 4.0.0
.devDependency
wait-on was updated from 2.1.2
to 4.0.1
.devDependency
wait-on was updated from 2.1.2
to 4.0.2
.devDependency
wait-on was updated from 2.1.2
to 5.0.0
.
Version 3.0.0 of wait-on was just published.
The version 3.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 wait-on.
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
v3.0.0Update packages which results in drop of support for Node 4.
V3+ requires node 6+
Updated:
Commits
The new version differs by 2 commits.
5e92e51
3.0.0
2ff1c15
update packages from 2.1.1
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: