-
Notifications
You must be signed in to change notification settings - Fork 43
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
renovate
wants to merge
1
commit into
dev
Choose a base branch
from
renovate/node-fetch-3.x
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+48
−35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for kleros-v2-contracts canceled.
|
❌ Deploy Preview for kleros-v2-testnet failed. Why did it fail? →
|
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
10 times, most recently
from
June 23, 2023 23:46
f09ed2d
to
4929ab7
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
15 times, most recently
from
June 29, 2023 14:48
f49233a
to
3a016c7
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
5 times, most recently
from
October 14, 2024 18:26
3ce7779
to
79d9fb6
Compare
❌ Deploy Preview for kleros-v2-testnet-devtools failed. Why did it fail? →
|
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
5 times, most recently
from
October 18, 2024 11:24
64dc43d
to
189f991
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
7 times, most recently
from
October 30, 2024 10:52
31c16ca
to
be790c8
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
8 times, most recently
from
November 6, 2024 20:09
3c353dc
to
a4d7e07
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
from
November 6, 2024 20:41
a4d7e07
to
98bed96
Compare
Code Climate has analyzed commit 98bed96 and detected 0 issues on this pull request. View more on Code Climate. |
Quality Gate passedIssues Measures |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.6.7
->^3.0.0
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
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
Body.body
into anode:stream
by @jimmywarting in https://github.com/node-fetch/node-fetch/pull/924url
toURL
by @dhritzkiv in https://github.com/node-fetch/node-fetch/pull/1318BodyMixin.formData()
and constructing bodies with FormData by @jimmywarting in https://github.com/node-fetch/node-fetch/pull/1314New 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
AbortError
(#1744) (9b9d458)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.
This PR was generated by Mend Renovate. View the repository job log.
PR-Codex overview
This PR focuses on updating dependencies in the
package.json
andyarn.lock
files, including major version upgrades and the addition of new packages.Detailed summary
node-fetch
from^2.6.7
to^3.0.0
.[email protected]
,[email protected]
,[email protected]
, and[email protected]
.nanoid
to^3.3.4
.whatwg-url@^5.0.0
.