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

Closed

Conversation

app-token-issuer-releng-renovate[bot]
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
node-fetch devDependencies major ^2.0.0 -> ^3.0.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


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

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 Renovate Bot.

@app-token-issuer-releng-renovate app-token-issuer-releng-renovate bot requested a review from a team as a code owner December 22, 2023 00:02
@app-token-issuer-releng-renovate app-token-issuer-releng-renovate bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from 092b348 to 57a1cad Compare December 26, 2023 00:02
@app-token-issuer-releng-renovate app-token-issuer-releng-renovate bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 24b6ee2 to 88bb503 Compare January 1, 2024 00:02
@momentmaker
Copy link
Contributor

looks like we have to continue to use node-fetch v2 for commonjs:
https://stackoverflow.com/questions/72706090/error-syntaxerror-cannot-use-import-statement-outside-a-module-when-using-nod

@momentmaker momentmaker closed this Jan 2, 2024
@app-token-issuer-releng-renovate
Copy link
Contributor Author

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.

@app-token-issuer-releng-renovate app-token-issuer-releng-renovate bot deleted the renovate/node-fetch-3.x branch January 3, 2024 00:02
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.

1 participant