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

fix(deps): update dependency node-fetch to v3 #116

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 19, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node-fetch 2.6.9 -> 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.

v2.7.0

Compare Source

Features

v2.6.13

Compare Source

Bug Fixes

v2.6.12

Compare Source

Bug Fixes

v2.6.11

Compare Source

Reverts

v2.6.10

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - "after 3am and before 10pm" (UTC), 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 added dependencies Updating dependencies major A major version change labels Jan 19, 2022
@renovate renovate bot changed the title fix(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 fix(deps): update dependency node-fetch to v3 Jan 23, 2022
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 0f48b1c to 19b1bed Compare March 7, 2022 18:43
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 19b1bed to 9fd9065 Compare March 12, 2022 00:15
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 9fd9065 to 3e27d0a Compare May 15, 2022 19:23
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 3e27d0a to 081f41e Compare June 18, 2022 22:03
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from bebdc8e to 8074f8a Compare March 17, 2023 04:05
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 8074f8a to 1971f2e Compare April 28, 2023 15:44
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 1971f2e to 61e4d2a Compare July 25, 2023 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Updating dependencies major A major version change
Development

Successfully merging this pull request may close these issues.

0 participants