fix(deps): update dependency node-fetch to v3.1.0 [security] - abandoned #678
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:
3.0.0
->3.1.0
GitHub Vulnerability Alerts
CVE-2022-0235
node-fetch forwards secure headers such as
authorization
,www-authenticate
,cookie
, &cookie2
when redirecting to a untrusted site.Release Notes
node-fetch/node-fetch (node-fetch)
v3.1.0
Compare Source
What's Changed
Body.body
into anode:stream
by @jimmywarting in https://github.com/node-fetch/node-fetch/pull/924url
toURL
by @dhritzkiv in https://github.com/node-fetch/node-fetch/pull/1318BodyMixin.formData()
and constructing bodies with FormData by @jimmywarting in https://github.com/node-fetch/node-fetch/pull/1314New Contributors
Full Changelog: node-fetch/node-fetch@v3.0.0...v3.1.0
Configuration
📅 Schedule: Branch creation - "" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 was generated by Mend Renovate. View the repository job log.