-
Notifications
You must be signed in to change notification settings - Fork 0
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 #152
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/node-fetch-3.x
base: main
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.
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
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
from
January 23, 2022 02:56
66c059a
to
ef72880
Compare
renovate
bot
changed the title
chore(deps): update dependency @types/node-fetch to v3
fix(deps): update dependency node-fetch to v3
Jan 23, 2022
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
5 times, most recently
from
January 26, 2022 21:32
2fdd32a
to
c9b1fc5
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
4 times, most recently
from
February 4, 2022 13:10
41887cc
to
bda2370
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
6 times, most recently
from
February 15, 2022 04:26
93753ee
to
1c0f464
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
3 times, most recently
from
March 1, 2022 14:25
2c56527
to
59e7ade
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
2 times, most recently
from
March 5, 2022 10:31
1163e60
to
0be20c3
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
2 times, most recently
from
March 16, 2022 09:49
5b5b40e
to
ea1da5d
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
3 times, most recently
from
March 23, 2022 19:03
c7fc474
to
9ccbf5b
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
2 times, most recently
from
March 31, 2022 15:01
2d6f19d
to
aa0fcab
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
from
April 13, 2022 01:11
aa0fcab
to
9df3fa3
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
2 times, most recently
from
December 14, 2022 15:26
e416bde
to
f410de9
Compare
renovate
bot
changed the title
fix(deps): update dependency node-fetch to v3
Update dependency node-fetch to v3
Dec 17, 2022
renovate
bot
changed the title
Update dependency node-fetch to v3
fix(deps): update dependency node-fetch to v3
Dec 17, 2022
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
from
December 20, 2022 20:44
f410de9
to
d5d81ae
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
4 times, most recently
from
January 14, 2023 08:21
7f206eb
to
6248976
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
from
January 17, 2023 22:22
6248976
to
3176934
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
from
January 25, 2023 02:35
3176934
to
ae19262
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
5 times, most recently
from
February 13, 2023 18:33
9a5236f
to
ce6c7fb
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
2 times, most recently
from
February 21, 2023 22:40
ecd5d31
to
8e283fe
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
from
March 10, 2023 16:41
8e283fe
to
f5fe01f
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
5 times, most recently
from
March 24, 2023 13:13
eb2eeef
to
fc5fa68
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
2 times, most recently
from
March 30, 2023 23:17
54d84ea
to
9b3e18b
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
from
May 16, 2023 17:06
9b3e18b
to
51c0b66
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
from
May 4, 2024 16:24
51c0b66
to
ab158af
Compare
renovate
bot
force-pushed
the
renovate/node-fetch-3.x
branch
from
May 4, 2024 19:21
ab158af
to
d33b65b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.1
->^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.
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.
This PR was generated by Mend Renovate. View the repository job log.