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

Update dependency node-fetch to v2.6.7 [SECURITY] #687

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 17, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node-fetch 2.6.1 -> 2.6.7 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2022-0235

node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor


Release Notes

node-fetch/node-fetch

v2.6.7

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

Full Changelog: node-fetch/node-fetch@v2.6.6...v2.6.7

v2.6.6

Compare Source

What's Changed

Full Changelog: node-fetch/node-fetch@v2.6.5...v2.6.6

v2.6.5

Compare Source

v2.6.4

Compare Source

v2.6.3

Compare Source

v2.6.2

Compare 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.

🔕 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependency-update A dependency was updated label Mar 17, 2022
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from 79d494c to 0c89638 Compare May 20, 2022 21:27
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] - autoclosed Jan 12, 2023
@renovate renovate bot closed this Jan 12, 2023
@renovate renovate bot deleted the renovate/npm-node-fetch-vulnerability branch January 12, 2023 03:51
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] - autoclosed Update dependency node-fetch to v2.6.7 [SECURITY] Jan 12, 2023
@renovate renovate bot reopened this Jan 12, 2023
@renovate renovate bot restored the renovate/npm-node-fetch-vulnerability branch January 12, 2023 07:44
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] - autoclosed Jan 15, 2023
@renovate renovate bot closed this Jan 15, 2023
@renovate renovate bot deleted the renovate/npm-node-fetch-vulnerability branch January 15, 2023 02:57
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] - autoclosed Update dependency node-fetch to v2.6.7 [SECURITY] Jan 15, 2023
@renovate renovate bot reopened this Jan 15, 2023
@renovate renovate bot restored the renovate/npm-node-fetch-vulnerability branch January 15, 2023 05:53
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] - autoclosed Feb 2, 2023
@renovate renovate bot closed this Feb 2, 2023
@renovate renovate bot deleted the renovate/npm-node-fetch-vulnerability branch February 2, 2023 03:43
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] - autoclosed Update dependency node-fetch to v2.6.7 [SECURITY] Feb 2, 2023
@renovate renovate bot reopened this Feb 2, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency-update A dependency was updated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant