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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 17, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node-fetch ^2.6.7 -> ^3.0.0 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

Configuration

📅 Schedule: Branch creation - "before 4am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, 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 the dependencies Pull requests that update a dependency file label Jun 17, 2023
@netlify
Copy link

netlify bot commented Jun 17, 2023

Deploy Preview for kleros-v2-contracts canceled.

Name Link
🔨 Latest commit b352ce6
🔍 Latest deploy log https://app.netlify.com/sites/kleros-v2-contracts/deploys/64f1c2b7a5ba9d0008a962b9

@netlify
Copy link

netlify bot commented Jun 17, 2023

Deploy Preview for kleros-v2-testnet failed. Why did it fail? →

Name Link
🔨 Latest commit 1b24442
🔍 Latest deploy log https://app.netlify.com/sites/kleros-v2-testnet/deploys/672d19f030c56400083db3ae

@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 10 times, most recently from f09ed2d to 4929ab7 Compare June 23, 2023 23:46
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 15 times, most recently from f49233a to 3a016c7 Compare June 29, 2023 14:48
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 4 times, most recently from 189f991 to 05d7a69 Compare October 23, 2024 15:47
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 6 times, most recently from 31c16ca to be790c8 Compare October 30, 2024 10:52
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 15 times, most recently from 02cc416 to e5da0e5 Compare November 7, 2024 19:46
Copy link
Contributor Author

renovate bot commented Nov 7, 2024

⚠️ 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: yarn.lock
node:fs:1371
  const result = binding.mkdir(
                         ^

Error: ENOENT: no such file or directory, mkdir '/home/ubuntu/.cache/node/corepack/v1'
    at mkdirSync (node:fs:1371:26)
    at getTemporaryFolder (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:21486:27)
    at download (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:21760:21)
    at installVersion (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:21854:61)
    at async Engine.ensurePackageManager (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:22310:32)
    at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:22410:25)
    at async Object.runMain (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:23096:5) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'mkdir',
  path: '/home/ubuntu/.cache/node/corepack/v1'
}

Node.js v20.18.0

Copy link

codeclimate bot commented Nov 7, 2024

Code Climate has analyzed commit 1b24442 and detected 0 issues on this pull request.

View more on Code Climate.

Copy link

sonarcloud bot commented Nov 7, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant