Update dependency node-fetch to v2.6.7 #10
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:
2.6.1
->2.6.7
By merging this PR, the issue #14 will be automatically resolved and closed:
Release Notes
node-fetch/node-fetch (node-fetch)
v2.6.7
Compare Source
Security patch release
Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred
What's Changed
Full Changelog: node-fetch/node-fetch@v2.6.6...v2.6.7
v2.6.6
Compare Source
What's Changed
Full Changelog: node-fetch/node-fetch@v2.6.5...v2.6.6
v2.6.5
Compare Source
v2.6.4
Compare Source
v2.6.3
Compare Source
v2.6.2
Compare Source
fixed main path in package.json