[deps]: Update node-fetch to v3 - #869
Conversation
bitwarden-bot
changed the title
|
Internal tracking:
|
renovate
Bot
changed the title
|
Great job! No new security vulnerabilities introduced in this pull request |
|
|
I'm not sure this should've been reopened. We previously closed it here: #316
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 EDIT: see #863 for Node 20 -> 22 upgrade |
33a9c42 to
9009be3
Compare
9009be3 to
a9356a9
Compare
a9356a9 to
fd3b909
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #869 +/- ##
=======================================
Coverage 16.01% 16.01%
=======================================
Files 67 67
Lines 2791 2791
Branches 481 481
=======================================
Hits 447 447
Misses 2306 2306
Partials 38 38 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Claude finished @renovate[bot]'s task —— View job Reviewing PR #869: Update node-fetch to v3 ✅Tasks
Review CompleteThe code review agent has analyzed the node-fetch v2 → v3 migration and posted detailed feedback directly on the PR. Summary:
The agent has posted 5 inline comments on specific code sections with detailed recommendations for improvement. |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
Edited/Blocked NotificationRenovate 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. |
|
As discussed in Slack, holding off until we've reviewed ESM support. The node upgrade may also make this obsolete. |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
3 participants
This PR contains the following updates:
2.7.0->3.3.2Release Notes
node-fetch/node-fetch (node-fetch)
v3.3.2Compare Source
Bug Fixes
v3.3.1Compare Source
Bug Fixes
v3.3.0Compare Source
Features
v3.2.10Compare Source
Bug Fixes
v3.2.9Compare Source
Bug Fixes
v3.2.8Compare Source
Bug Fixes
v3.2.7Compare Source
Bug Fixes
v3.2.6Compare Source
Bug Fixes
v3.2.5Compare Source
Bug Fixes
v3.2.4Compare Source
Bug Fixes
v3.2.3Compare Source
Bug Fixes
v3.2.2Compare Source
Bug Fixes
v3.2.1Compare Source
Bug Fixes
v3.2.0Compare Source
Features
v3.1.1Compare 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.0Compare Source
What's Changed
Body.bodyinto anode:streamby @jimmywarting in #924urltoURLby @dhritzkiv in #1318BodyMixin.formData()and constructing bodies with FormData by @jimmywarting in #1314New Contributors
Full Changelog: node-fetch/node-fetch@v3.0.0...v3.1.0
v3.0.0Compare 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.
This PR was generated by Mend Renovate. View the repository job log.