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

Update dependency node-fetch to v3 #305

Merged
merged 1 commit into from Oct 8, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 8, 2023

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
node-fetch ^2.6.0 -> ^3.0.0 age adoption passing confidence

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please 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.


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 these updates 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
Copy link
Contributor Author

renovate bot commented Oct 8, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
[10:18:28.783] INFO (10): Installing tool node v18.18.0...
v18.18.0
9.8.1
0.19.0
[10:18:31.217] INFO (10): Installed tool node in 2.4s.
[10:18:32.033] INFO (53): Installing tool pnpm v8.8.0...
8.8.0
[10:18:33.477] INFO (53): Installed tool pnpm in 1.4s.
 ERROR  Unexpected number in JSON at position 7388 while parsing '{  "name": "nextjs-project",  "version' in /tmp/worker/854a80/481815/repos/github/X-oss-byte/Canary-nextjs/package.json 

  183 |     "playwright-chromium": "1.38.1",
  184 |     "plop": "3.0.5",
> 185 |  01-30-Add_test_for_issue_45393
      |  ^
  186 |     "postcss-nested": "4.2.3",
  187 |     "postcss-pseudoelements": "5.0.0",
  188 |     "postcss-short-size": "4.0.0",

For help, run: pnpm help install

@stackblitz
Copy link

stackblitz bot commented Oct 8, 2023

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@changeset-bot
Copy link

changeset-bot bot commented Oct 8, 2023

⚠️ No Changeset found

Latest commit: f8714e7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@kodiakhq kodiakhq bot merged commit 96da2de into 01-30-Add_test_for_issue_45393 Oct 8, 2023
1 of 3 checks passed
@kodiakhq kodiakhq bot deleted the renovate/node-fetch-3.x branch October 8, 2023 10:18
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.

None yet

0 participants