fix: update dependency wait-on to v5 #257
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.0.0
->5.0.3
Release Notes
jeffbski/wait-on
v5.0.3
Compare Source
update to lodash@4.17.19
v5.0.2
Compare Source
lodash@4.17.18 update which resolved some potential lodash vulnerabilities
v5.0.1
Compare Source
Force axios to use http adapter to keep logs clean if jest/jsdom are used with the wait-on API.
If jest/jsdom is used then a polyfill for xhr is created which will cause axios to default the adapter to it. Since jsdom logs all errors use of wait-on will have any failed attempts to connect logged which is rather noisy and misleading.
By forcing axios to use the node.js http adapter instead this problem is bypassed keeping logs clean.
v5.0.0
Compare Source
Switch HTTP client from request to axios
Since the
request
package is no longer receiving updates, wait-on switched to usingaxios
. Attempt to keep the same wait-on options as much as possible.These breaking changes occurred in the switch:
followRedirect: true|false
(defaults to true).httpSignature
is not implemented in axios and now not available. (If this feature is still desired, please help by providing a pull request to implement it.)auth
allows onlyusername
andpassword
but not the previous aliasesuser
andpass
add optional validateStatus fn property
If
validateStatus
property is provided in theconfig and set to a function, it will use this to
validate whether a status is valid.
The default validateStatus if not provided is
To also allow a 401 unauthorized as a valid status
v4.0.2
Compare Source
Updated dependencies which closed security vulnerability in minimist and acorn.
v4.0.1
Compare Source
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.