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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 29, 2022

WhiteSource Renovate

This PR contains the following updates:

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

Release Notes

node-fetch/node-fetch

v3.2.3

Compare Source

Bug Fixes

v3.2.2

Compare Source

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: "every weekend" (UTC).

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

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

@renovate renovate bot added the renovate label Mar 29, 2022
@scissorsneedfoodtoo
Copy link
Contributor

Closing this in favor node-fetch v2, at least for the time being.

As mentioned in the upgrade guide node-fetch v2 will continue to receive critical bug fixes.

If we decide to move to v3 in the future, we can use dynamic imports wherever the package is required.

@scissorsneedfoodtoo scissorsneedfoodtoo deleted the renovate/node-fetch-3.x branch March 29, 2022 05:36
@scissorsneedfoodtoo scissorsneedfoodtoo changed the title chore(deps): update dependency node-fetch to v3 chore(deps): update dependency node-fetch to v3 - closed Mar 29, 2022
@scissorsneedfoodtoo scissorsneedfoodtoo changed the title chore(deps): update dependency node-fetch to v3 - closed chore(deps): update dependency node-fetch to v3 Mar 29, 2022
@renovate
Copy link
Contributor Author

renovate bot commented Mar 29, 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
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants