Skip to content

Update dependency node-fetch to v3 - #24

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

Update dependency node-fetch to v3#24
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/node-fetch-3.x

Conversation

@renovate

@renovate renovate Bot commented Aug 31, 2021

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
node-fetch ^2.6.1 -> ^3.0.0 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.

v2.7.0

Compare Source

Features

v2.6.13

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - "before 7am every weekday" in timezone Europe/Brussels, 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 force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from a6bf3a4 to 37d8e0f Compare September 8, 2021 02:15
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from 1f7ac1d to ea37519 Compare September 22, 2021 02:11
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from e63a7ff to b192240 Compare September 30, 2021 01:27
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 39d69a2 to 8e30cf8 Compare October 13, 2021 01:57
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 1a0888e to 4aac1a3 Compare October 15, 2021 02:10
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from 5d791a1 to 4b88745 Compare October 26, 2021 08:29
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from b3c729b to c42e0d7 Compare November 10, 2021 03:34
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 4 times, most recently from b0c9cc7 to 6c94806 Compare November 24, 2021 02:58
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from ff9a05c to 3c5750f Compare December 6, 2021 04:22
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from ced51b2 to 35f85a9 Compare December 15, 2021 03:30
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 4 times, most recently from 3f6d1a4 to 810eb1d Compare December 22, 2021 04:45
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch from 810eb1d to 65dda09 Compare December 24, 2021 03:47
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from aaa4bf3 to ad03854 Compare January 11, 2022 04:39
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 1151c5c to 973adb8 Compare January 19, 2022 02:53
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 5 times, most recently from 92d84f6 to 91cdfdb Compare February 15, 2022 04:26
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch from 91cdfdb to ecd1fa5 Compare February 16, 2022 02:58
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch from ecd1fa5 to 2cfb417 Compare April 15, 2022 07:35
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch from 2cfb417 to c152bac Compare March 16, 2023 02:38
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch from c152bac to f79e64c Compare May 10, 2023 04:49
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch from f79e64c to 7dd3041 Compare June 30, 2023 04:38
@renovate renovate Bot changed the title Update dependency node-fetch to v3 Update dependency node-fetch to v3 - autoclosed Dec 8, 2024
@renovate renovate Bot closed this Dec 8, 2024
@renovate
renovate Bot deleted the renovate/node-fetch-3.x branch December 8, 2024 18:29
@renovate renovate Bot changed the title Update dependency node-fetch to v3 - autoclosed Update dependency node-fetch to v3 Dec 13, 2024
@renovate renovate Bot reopened this Dec 13, 2024
@renovate

renovate Bot commented Dec 13, 2024

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: base-registries-event-stream@4.0.0
npm ERR! Found: eslint@8.57.1
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"8.57.1" from the root project
npm ERR!   peer eslint@"^8.57.0 || ^9.0.0" from @typescript-eslint/eslint-plugin@8.47.0
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     peerOptional @typescript-eslint/eslint-plugin@"8" from eslint-plugin-unused-imports@4.0.0
npm ERR!     node_modules/eslint-plugin-unused-imports
npm ERR!       dev eslint-plugin-unused-imports@"4.0.0" from the root project
npm ERR!   1 more (@typescript-eslint/parser)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"9" from eslint-plugin-unused-imports@4.0.0
npm ERR! node_modules/eslint-plugin-unused-imports
npm ERR!   dev eslint-plugin-unused-imports@"4.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-11-18T10_16_33_473Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 6a91262 to 841eae3 Compare August 13, 2025 15:44
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch from 841eae3 to 7da3d7d Compare August 19, 2025 16:15
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch from 7da3d7d to 48c6b6d Compare September 25, 2025 18:11
@renovate
renovate Bot force-pushed the renovate/node-fetch-3.x branch from 48c6b6d to ca501a1 Compare November 10, 2025 23:40
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