Bump node-fetch from 2.6.1 to 2.6.7 #1110
Open
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-pagopa[bot]](https://avatars.githubusercontent.com/u/57742367?s=60&v=4){kind=small}
Jira Pull request LinkIt seems this Pull Request has no issues that refers to Jira!!! |
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
3 times, most recently
from
42946a1
to
69ed42d
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
2 times, most recently
from
1e14f3f
to
600d310
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
2 times, most recently
from
e3a2ef4
to
71e5729
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
3 times, most recently
from
ac6575e
to
a2bfd2a
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
2 times, most recently
from
9984ab5
to
761aab4
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
4 times, most recently
from
e0b1c74
to
870f834
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
2 times, most recently
from
e2498a1
to
f080f13
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
4 times, most recently
from
22c3e9a
to
d1b0f0d
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
from
d1b0f0d
to
59df0f8
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
2 times, most recently
from
4d1e866
to
f1cf78f
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
2 times, most recently
from
fbf7830
to
a978e0e
Compare
|
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
3 times, most recently
from
70a5e48
to
4068bf2
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
from
4068bf2
to
9d16d72
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
2 times, most recently
from
961bcd2
to
90638e2
Compare
renovate-pagopa
bot
force-pushed
the
renovate/node-fetch-to-2.6.7
branch
from
90638e2
to
3ce4978
Compare
|
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.1->2.6.7For further information on security, please refer to the Confluence page link
Release Notes
node-fetch/node-fetch (node-fetch)
v2.6.7Compare 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
Full Changelog: node-fetch/node-fetch@v2.6.6...v2.6.7
v2.6.6Compare Source
What's Changed
Full Changelog: node-fetch/node-fetch@v2.6.5...v2.6.6
v2.6.5Compare Source
v2.6.4Compare Source
v2.6.3Compare Source
v2.6.2Compare Source
fixed main path in package.json
Configuration
📅 Schedule: Branch creation - "" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.