[Snyk] Upgrade node-fetch from 2.1.1 to 2.7.0 #803
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade node-fetch from 2.1.1 to 2.7.0. See this package in npm: node-fetch See this project in Snyk: https://app.snyk.io/org/ali8668/project/d2bc4c8e-fae4-4f5a-be7d-a7804c850973?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade node-fetch from 2.1.1 to 2.7.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 22 versions ahead of your current version.
The recommended version was released 9 months ago, on 2023-08-23.
The recommended version fixes:
SNYK-JS-NODEFETCH-2342118
Why? Has a fix available, CVSS 6.5
SNYK-JS-NODEFETCH-674311
Why? Has a fix available, CVSS 6.5
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: node-fetch
-
2.7.0 - 2023-08-23
-
2.6.13 - 2023-08-18
- Remove the default connection close header (#1765) (65ae25a), closes #1735 #1473 #1736
-
2.6.12 - 2023-06-29
- socket variable testing for undefined (#1726) (8bc3a7c)
-
2.6.11 - 2023-05-09
- Revert "fix: handle bom in text and json (#1739)" (#1741) (afb36f6), closes #1739 #1741
-
2.6.10 - 2023-05-08
- handle bom in text and json (#1739) (29909d7)
-
2.6.9 - 2023-01-30
- "global is not defined" (#1704) (70f592d)
-
2.6.8 - 2023-01-13
- headers: don't forward secure headers on protocol change (#1605) (fddad0e), closes #1599
- premature close with chunked transfer encoding and for async iterators in Node 12 (#1172) (50536d1), closes #1064 /github.com/node-fetch/node-fetch/pull/1064#issuecomment-849167400
- prevent hoisting of the undefined
-
2.6.7 - 2022-01-16
-
2.6.6 - 2021-10-31
-
2.6.5 - 2021-09-22
-
2.6.4 - 2021-09-21
-
2.6.3 - 2021-09-20
-
2.6.2 - 2021-09-06
-
2.6.1 - 2020-09-05
-
2.6.0 - 2019-05-16
-
2.5.0 - 2019-05-01
-
2.4.1 - 2019-04-27
-
2.4.0 - 2019-04-26
-
2.3.0 - 2018-11-13
-
2.2.1 - 2018-11-05
-
2.2.0 - 2018-07-22
-
2.1.2 - 2018-03-25
-
2.1.1 - 2018-03-05
from node-fetch GitHub release notes2.7.0 (2023-08-23)
Features
AbortError(#1744) (9b9d458)2.6.13 (2023-08-18)
Bug Fixes
2.6.12 (2023-06-29)
Bug Fixes
2.6.11 (2023-05-09)
Reverts
2.6.10 (2023-05-08)
Bug Fixes
2.6.9 (2023-01-30)
Bug Fixes
2.6.8 (2023-01-13)
Bug Fixes
globalvariable inbrowser.js(#1534) (8bb6e31)Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs
Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.