Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[deps]: Update node-fetch to v3 #316

Closed
wants to merge 2 commits into from
Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 23, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node-fetch 2.7.0 -> 3.3.2 age adoption passing 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 weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, 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. View repository job log here.

@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 8 times, most recently from fb8b945 to fa27efb Compare May 31, 2023 19:11
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 915d469 to cd38cc1 Compare June 6, 2023 10:23
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 7 times, most recently from 8774714 to 10bd03b Compare June 16, 2023 13:18
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from a863d5a to b4f9111 Compare June 21, 2023 13:04
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from b4f9111 to 2ae78e2 Compare July 17, 2023 22:24
@renovate renovate bot requested a review from a team as a code owner July 17, 2023 22:24
@bitwarden-bot
Copy link

bitwarden-bot commented Jul 17, 2023

Logo
Checkmarx One – Scan Summary & Detailsbc912a59-2461-4ae0-9a20-d3a37658a930

No New Or Fixed Issues Found

@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 2ae78e2 to 75c5c88 Compare July 25, 2023 12:38
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from 93c9b32 to 8a67723 Compare August 30, 2023 18:45
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from 8140656 to 2f184a5 Compare September 18, 2023 14:48
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 5 times, most recently from 546cdae to f2310df Compare November 1, 2023 17:35
@renovate renovate bot changed the title Update dependency node-fetch to v3 [deps]: Update node-fetch to v3 Dec 5, 2023
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from f9f335c to c5b0177 Compare December 12, 2023 15:27
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 4 times, most recently from ef7a476 to 4e9c55f Compare December 15, 2023 14:11
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 05f6e0e to e6dce44 Compare February 1, 2024 19:12
Copy link
Contributor Author

renovate bot commented Feb 1, 2024

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.

@addisonbeck addisonbeck force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 44d4c8f to 0f7ae50 Compare February 2, 2024 12:39
@addisonbeck
Copy link
Contributor

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.

Closing this one.

@addisonbeck addisonbeck closed this Feb 2, 2024
Copy link
Contributor Author

renovate bot commented Feb 2, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/node-fetch-3.x branch February 2, 2024 12:47
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.

2 participants