Open renovate[bot] opened 2 years ago
Merging #1435 (296287b) into develop (d01a0b3) will not change coverage. The diff coverage is
n/a
.:exclamation: Current head 296287b differs from pull request most recent head 2ac5d7b. Consider uploading reports for the commit 2ac5d7b to get more accurate results
@@ Coverage Diff @@
## develop #1435 +/- ##
========================================
Coverage 49.53% 49.53%
========================================
Files 249 249
Lines 2158 2158
========================================
Hits 1069 1069
Misses 1089 1089
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:
The artifact failure details are included below:
Error response from daemon: Get https://registry-1.docker.io/v2/renovate/node/manifests/10.21.0: received unexpected HTTP status: 503 Service Unavailable
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.
This PR contains the following updates:
2.6.0
->2.6.1
GitHub Vulnerability Alerts
CVE-2020-15168
Impact
Node Fetch did not honor the
size
option after following a redirect, which means that when a content size was over the limit, aFetchError
would never get thrown and the process would end without failure.For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after
fetch()
has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.Patches
We released patched versions for both stable and beta channels:
v2
: 2.6.1v3
: 3.0.0-beta.9Workarounds
None, it is strongly recommended to update as soon as possible.
For more information
If you have any questions or comments about this advisory:
Release Notes
node-fetch/node-fetch
### [`v2.6.1`](https://togithub.com/node-fetch/node-fetch/releases/tag/v2.6.1) [Compare Source](https://togithub.com/node-fetch/node-fetch/compare/v2.6.0...v2.6.1) **This is an important security release. It is strongly recommended to update as soon as possible.** See [CHANGELOG](https://togithub.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261) for details.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.
This PR has been generated by Mend Renovate. View repository job log here.