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

Open
wants to merge 30 commits into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 5, 2024

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 - "after 1am and before 6am" in timezone CET, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

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 force-pushed the renovate/node-fetch-3.x branch from 0f3bd2d to 5c33f49 Compare January 5, 2024 04:29
@vio vio force-pushed the update-dependencies branch from 210587c to cb9c141 Compare January 8, 2024 09:37
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 5c33f49 to 75f9e47 Compare January 8, 2024 09:38
@vio vio force-pushed the update-dependencies branch from ad12a7e to 9806431 Compare January 8, 2024 09:44
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 75f9e47 to 7aa2250 Compare January 8, 2024 09:45
@vio vio force-pushed the update-dependencies branch from 3e996aa to 51a75bb Compare January 8, 2024 10:49
Base automatically changed from update-dependencies to master January 8, 2024 10:51
@renovate renovate bot changed the title fix(deps): update dependency node-fetch to v3 fix(deps): update dependency node-fetch to v3 - autoclosed Jan 8, 2024
@renovate renovate bot closed this Jan 8, 2024
@renovate renovate bot deleted the renovate/node-fetch-3.x branch January 8, 2024 10:52
@renovate renovate bot restored the renovate/node-fetch-3.x branch January 8, 2024 16:04
@renovate renovate bot changed the title fix(deps): update dependency node-fetch to v3 - autoclosed fix(deps): update dependency node-fetch to v3 Jan 8, 2024
@renovate renovate bot reopened this Jan 8, 2024
Copy link
Contributor Author

renovate bot commented Jan 8, 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.

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.

1 participant