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 #621

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.0.0 age adoption passing confidence

Release Notes

node-fetch/node-fetch

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 - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR label Aug 31, 2021
Copy link
Contributor

@gr2m gr2m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are not ready for node-fetch v3, as it's a native ES Module. We will be once the work is done in https://github.com/octokit/octokit-next.js

@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 3a3e932 to 1fe67da Compare September 2, 2021 00:01
@wolfy1339 wolfy1339 added this to the v10 milestone Sep 2, 2021
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 6 times, most recently from 8c94987 to 46dc3d6 Compare September 8, 2021 19:04
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 7 times, most recently from 919578c to 55bf9f6 Compare September 16, 2021 16:45
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 4 times, most recently from 800c565 to be259ce Compare September 20, 2021 18:34
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 4 times, most recently from 5462adc to 797893a Compare October 4, 2021 16:21
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from e39f6e8 to 0ea23cb Compare October 6, 2021 18:42
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 4 times, most recently from c89e3af to 1f70cc8 Compare April 17, 2023 16:26
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 1140acc to ba446fa Compare April 24, 2023 17:26
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from ba446fa to 69c1035 Compare May 1, 2023 17:47
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from bf32de8 to b01c590 Compare May 15, 2023 15:40
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 4a3af37 to 0973c65 Compare May 22, 2023 14:12
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from 327f959 to edd9840 Compare May 29, 2023 03:43
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from e0e706d to cf530dd Compare June 7, 2023 16:01
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 4 times, most recently from ccfc842 to 6193234 Compare June 12, 2023 22:00
wolfy1339 added a commit that referenced this pull request Jun 12, 2023
@wolfy1339 wolfy1339 mentioned this pull request Jun 12, 2023
5 tasks
@wolfy1339 wolfy1339 removed the Status: Triage This is being looked at and prioritized label Jun 12, 2023
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 6193234 to c8aefa6 Compare June 13, 2023 18:28
wolfy1339 added a commit that referenced this pull request Jun 13, 2023
@renovate renovate bot deleted the renovate/node-fetch-3.x branch June 13, 2023 18:56
@github-actions
Copy link
Contributor

🎉 This issue has been resolved in version 12.0.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
esm-blocked Temporary label to denote esm dependency blocker released Status: Blocked Blocked by GitHub's API or other external factors Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants