Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 12, 2025

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

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: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner September 12, 2025 18:58
@renovate renovate bot requested a review from JimmyVo16 September 12, 2025 18:58
@bitwarden-bot bitwarden-bot changed the title [deps]: Update node-fetch to v3 [PM-25711] [deps]: Update node-fetch to v3 Sep 13, 2025
@bitwarden-bot
Copy link

Internal tracking:

@renovate renovate bot changed the title [PM-25711] [deps]: Update node-fetch to v3 [deps]: Update node-fetch to v3 Sep 13, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Sep 17, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 17, 2025

Logo
Checkmarx One – Scan Summary & Details9387a933-a4c5-4a0e-ae84-c68f93847249

Great job! No new security vulnerabilities introduced in this pull request

@sonarqubecloud
Copy link

@eliykat
Copy link
Member

eliykat commented Oct 1, 2025

I'm not sure this should've been reopened. We previously closed it here: #316

Node fetch 3 is not compatible with CommonJs, and we can't use it. The better solution here would be to replace this package with the native fetch API, but we can't do that until we upgrade node a bit.

I agree with that assessment, but we need node >= 21 to be able to use the native fetch: https://nodejs.org/docs/latest-v21.x/api/globals.html#fetch

So... almost! but not yet

@vincentsalucci vincentsalucci requested a review from r-tome October 29, 2025 20:32
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.

4 participants