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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 31, 2021

This PR contains the following updates:

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

v2.6.9

Compare Source

Bug Fixes

v2.6.8

Compare Source

Bug Fixes

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovate label Aug 31, 2021
@commit-lint
Copy link

commit-lint bot commented Aug 31, 2021

Bug Fixes

  • deps: update dependency node-fetch to v3 (f6fea69)

Contributors

renovate[bot]

Commit-Lint commands

You can trigger Commit-Lint actions by commenting on this PR:

  • @Commit-Lint merge patch will merge dependabot PR on "patch" versions (X.X.Y - Y change)
  • @Commit-Lint merge minor will merge dependabot PR on "minor" versions (X.Y.Y - Y change)
  • @Commit-Lint merge major will merge dependabot PR on "major" versions (Y.Y.Y - Y change)
  • @Commit-Lint merge disable will desactivate merge dependabot PR
  • @Commit-Lint review will approve dependabot PR
  • @Commit-Lint stop review will stop approve dependabot PR

@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 8f9615e to 745a467 Compare November 14, 2021 02:33
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from c02f737 to 05a87a7 Compare January 20, 2022 22:36
@renovate renovate bot changed the title fix(deps): update dependency node-fetch to v3 fix(deps): update dependency node-fetch to v3 - autoclosed Jan 22, 2022
@renovate renovate bot closed this Jan 22, 2022
@renovate renovate bot deleted the renovate/node-fetch-3.x branch January 22, 2022 12:52
@renovate renovate bot changed the title fix(deps): update dependency node-fetch to v3 - autoclosed fix(deps): update dependency node-fetch to v3 Jan 23, 2022
@renovate renovate bot reopened this Jan 23, 2022
@renovate renovate bot restored the renovate/node-fetch-3.x branch January 23, 2022 03:41
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 05a87a7 to b53f3a5 Compare March 7, 2022 14:09
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from b53f3a5 to d3403ad Compare March 26, 2022 12:17
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from d3403ad to b4b52a9 Compare May 15, 2022 20:37
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from b4b52a9 to 21ff021 Compare June 18, 2022 14:56
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 2 times, most recently from 859d9be to 4278154 Compare July 12, 2022 01:12
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch 3 times, most recently from 72a32f9 to 67fa875 Compare July 18, 2022 20:48
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from 67fa875 to 029e4d7 Compare July 31, 2022 10:16
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from e39d71f to ff8a4a6 Compare March 16, 2023 06:42
@renovate renovate bot force-pushed the renovate/node-fetch-3.x branch from ff8a4a6 to f6fea69 Compare July 25, 2023 12:39
@renovate
Copy link
Contributor Author

renovate bot commented Jul 25, 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: package-lock.json
/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @eclass/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/eslint-plugin-sonarjs
npm WARN   dev eslint-plugin-sonarjs@"0.13.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer eslint-plugin-sonarjs@"^0.4.0 || ^0.5.0" from @eclass/[email protected]
npm WARN node_modules/@eclass/eslint-config
npm WARN   dev @eclass/eslint-config@"1.3.1" from the root project
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @eclass/[email protected]
npm ERR! Found: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR!   dev @typescript-eslint/eslint-plugin@"3.10.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @typescript-eslint/eslint-plugin@"^2.9.0" from @eclass/[email protected]
npm ERR! node_modules/@eclass/eslint-config
npm ERR!   dev @eclass/eslint-config@"1.3.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR!   peer @typescript-eslint/eslint-plugin@"^2.9.0" from @eclass/[email protected]
npm ERR!   node_modules/@eclass/eslint-config
npm ERR!     dev @eclass/eslint-config@"1.3.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/f94c18/32e74f/cache/others/npm/_logs/2023-07-25T12_39_34_242Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/f94c18/32e74f/cache/others/npm/_logs/2023-07-25T12_39_34_242Z-debug-0.log

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