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

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 31, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node-fetch 2.6.7 -> 3.2.10 age adoption passing confidence

Release Notes

node-fetch/node-fetch

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 weekday" in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled due to failing status checks.

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, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the renovatebot label Aug 31, 2021
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 8 times, most recently from 5b6cef2 to 8625f21 Compare September 6, 2021 15:39
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 9 times, most recently from 09cac77 to 3b3e1c0 Compare September 17, 2021 04:58
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 5 times, most recently from 178d94a to 5375ee8 Compare September 22, 2021 15:03
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from 596f0c9 to 4800c92 Compare October 1, 2021 02:21
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 4 times, most recently from d5ba787 to 260e001 Compare October 19, 2021 04:28
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from 4564d10 to e6c7786 Compare December 1, 2021 20:33
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 0121b22 to 10d1544 Compare January 20, 2022 22:04
@renovate renovate bot changed the title chore(deps): update dependency node-fetch to v3 chore(deps): update dependency @types/node-fetch to v3 Jan 22, 2022
@renovate renovate bot changed the title chore(deps): update dependency @types/node-fetch to v3 chore(deps): update dependency node-fetch to v3 Jan 23, 2022
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 10d1544 to c8218e7 Compare March 7, 2022 09:53
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from c8218e7 to fa6b58b Compare March 26, 2022 14:53
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from fa6b58b to 0c60649 Compare May 16, 2022 02:35
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 0c60649 to c9f9652 Compare June 18, 2022 16:11
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 5 times, most recently from 8703c44 to 5f54404 Compare September 29, 2022 07:41
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 4 times, most recently from d4e9812 to 1902656 Compare October 5, 2022 03:33
@nguyentoanit
Copy link
Contributor

Looks like node-fetch v3 only works as an ESM. See node-fetch/node-fetch#1289 (comment)

@moltar
Copy link
Contributor

moltar commented Oct 5, 2022

Ah, yes! Same issue on the AD side, and I had to downgrade it to the most recent non-ESM version. Please see AD version and install the same.

@nguyentoanit
Copy link
Contributor

Ah, yes! Same issue on the AD side, and I had to downgrade it to the most recent non-ESM version. Please see AD version and install the same.

Same to AD side now. Skip this update?

@moltar
Copy link
Contributor

moltar commented Oct 5, 2022

Ah, yes! Same issue on the AD side, and I had to downgrade it to the most recent non-ESM version. Please see AD version and install the same.

Same to AD side now. Skip this update?

yes

@moltar moltar closed this Oct 5, 2022
@moltar moltar deleted the renovate/node-fetch-3.x branch October 5, 2022 09:38
@renovate
Copy link
Contributor Author

renovate bot commented Oct 5, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants