🚨 [security] Update node-fetch: 3.1.1 → 3.2.10 (minor) #66
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ node-fetch (3.1.1 → 3.2.10) · Repo · Changelog
Security Advisories 🚨
🚨 node-fetch Inefficient Regular Expression Complexity
Release Notes
3.2.10
3.2.9
3.2.8
3.2.7
3.2.6
3.2.5
3.2.4
3.2.3
3.2.2
3.2.1
3.2.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 30 commits:
fix: ReDoS referrer (#1611)
fix(Headers): don't forward secure headers on protocol change (#1599)
chore: remove triple-slash directives from typings (#1285) (#1287)
fix spelling (#1602)
fix: possibly flaky test (#1523)
fix: always warn Request.data (#1550)
fix: undefined reference to response.body when aborted (#1578)
fix: use space in accept-encoding values (#1572)
docs: fix formdata code example (#1562)
docs(readme): response.clone() is not async (#1560)
Fix leaking listeners (#1295) (#1474)
fix: don't uppercase unknown methods (#1542)
Fix Code of Conduct link in Readme. (#1532)
docs: Fix link markup to Options definition (#1525)
fix: handle bom in text and json (#1482)
fix: add missing formdata export to types (#1518)
fix: cancel request example import (#1513)
Replace changelog with valid url (#1506)
types: support `agent: false` (#1502)
chore: fix typo in credential error message (#1496)
docs(readme): fix typo (#1489)
docs: remove the changelog (#1464)
core: move support and feature to discussion (#1471)
docs: update formdata example (#1465)
feat: export Blob, File and FormData + utilities (#1463)
ci: semantic-release (#1270)
test: Modernize and convert some test in `main.js` to async/await (#1456)
test: Update major busboy version (#1457)
Handle zero-length OK deflate responses (master) (#965)
Simplify check in isDomainOrSubdomain (#1455)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands