Skip to content

chore(deps): update dependency node-fetch to v3 - #10378

Open
metamask-ci[bot] wants to merge 1 commit into
mainfrom
renovate/node-fetch-3.x
Open

metamask-ci[bot] wants to merge 1 commit into
mainfrom
renovate/node-fetch-3.x

Conversation

@metamask-ci

@metamask-ci metamask-ci Bot commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
node-fetch ^2.7.0 → ^3.3.2 age confidence

Release Notes

node-fetch/node-fetch (node-fetch)

v3.3.2

Compare Source

Bug Fixes

v3.3.1

Compare Source

Bug Fixes

v3.3.0

Compare Source

Features

v3.2.10

Compare Source

Bug Fixes

v3.2.9

Compare Source

Bug Fixes
  • Headers: don't forward secure headers on protocol change (#​1599) (e87b093)

v3.2.8

Compare Source

Bug Fixes

v3.2.7

Compare Source

Bug Fixes

v3.2.6

Compare Source

Bug Fixes

v3.2.5

Compare Source

Bug Fixes

v3.2.4

Compare Source

Bug Fixes

v3.2.3

Compare Source

Bug Fixes

v3.2.2

Compare Source

Bug Fixes

v3.2.1

Compare Source

Bug Fixes

v3.2.0

Compare Source

Features

v3.1.1

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

New Contributors

Full Changelog: node-fetch/node-fetch@v3.1.0...v3.1.1

v3.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: node-fetch/node-fetch@v3.0.0...v3.1.0

v3.0.0

Compare Source

version 3 is going out of a long beta period and switches to stable

One major change is that it's now a ESM only package
See changelog for more information about all the changes.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@metamask-ci
metamask-ci Bot requested review from a team as code owners September 22, 2026 21:07
@metamask-ci
metamask-ci Bot deployed to dependabot September 22, 2026 21:07 Active
@metamask-ci
metamask-ci Bot deployed to default-branch September 22, 2026 21:07 Active
@socket-security

socket-security Bot commented Sep 22, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednode-fetch@​3.3.29910010085100

View full report

@socket-security

socket-security Bot commented Sep 22, 2026 •

Copy link
Copy Markdown

Warning

MetaMask internal reviewing guidelines:

  • Do not ignore-all
  • Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
  • Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
    @SocketSecurity ignore npm/PACKAGE@VERSION
Action Severity Alert  (click "▶" to expand/collapse)
Warn Medium
Network access: npm formdata-polyfill in module globalThis["fetch"]

Module: globalThis["fetch"]

Location: Package overview

From: packages/network-controller/package.json → npm/node-fetch@3.3.2 → npm/formdata-polyfill@4.0.10

ℹ Read more on: This package | This alert | What is network access?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/formdata-polyfill@4.0.10. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit e259150. Configure here.

"lodash-es": "^4.17.21",
"nock": "^13.5.6",
"node-fetch": "^2.7.0",
"node-fetch": "^3.3.2",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ESM upgrade breaks Jest test imports

High Severity

Bumping node-fetch to v3 makes the package ESM-only, but Jest still compiles these tests to CommonJS. Existing FetchError imports will throw ERR_REQUIRE_ESM on Node 22, which CI still runs.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit e259150. Configure here.

@metamask-ci
metamask-ci Bot force-pushed the renovate/node-fetch-3.x branch from e259150 to af936f4 Compare September 23, 2026 06:17
@metamask-ci
metamask-ci Bot force-pushed the renovate/node-fetch-3.x branch from af936f4 to b6b3df5 Compare September 25, 2026 06:18
@metamask-ci
metamask-ci Bot deployed to dependabot September 25, 2026 06:18 Active

This branch was successfully deployed

2 active (1 outdated) deployments
dependabot — b6b3df5c Deployed Sep 25, 2026 by metamask-ci[bot] via Repair constraints, lockfile and changelogs #171
default-branch — e2591500 Deployed Sep 22, 2026 by metamask-ci[bot] via Determine whether this PR is a release PR #4435
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants