This repository was archived by the owner on Jun 7, 2022. It is now read-only.
Update dependency npm-registry-fetch to v8.1.1 [SECURITY]#387
Closed
renovate[bot] wants to merge 0 commit intomasterfrom
Closed
Update dependency npm-registry-fetch to v8.1.1 [SECURITY]#387renovate[bot] wants to merge 0 commit intomasterfrom
renovate[bot] wants to merge 0 commit intomasterfrom
Conversation
8a2f010 to
7a06a84
Compare
a609225 to
3e9ad05
Compare
d75965e to
06ce326
Compare
2c90c58 to
7906e4b
Compare
7906e4b to
c3b69b5
Compare
c3b69b5 to
341a5d0
Compare
341a5d0 to
2ab210c
Compare
0dfe00d to
d5bd8c8
Compare
fb0dc9a to
594a2e2
Compare
594a2e2 to
7d44a89
Compare
7c96194 to
f61426c
Compare
f61426c to
47c7f9d
Compare
Contributor
Author
Renovate Ignore NotificationAs this PR has been closed unmerged, Renovate will now ignore this update (^8.0.0). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
GitHub Vulnerability Alerts
GHSA-jmqm-f2gx-4fjv
Affected versions of
npm-registry-fetchare vulnerable to an information exposure vulnerability through log files. The cli supports URLs like<protocol>://[<user>[:<password>]@​]<hostname>[:<port>][:][/]<path>. The password value is not redacted and is printed to stdout and also to any generated log files.Release Notes
npm/registry-fetch
v8.1.1Compare Source
v8.1.0Compare Source
Features
8.0.3 (2020-05-13)
Bug Fixes
8.0.2 (2020-05-04)
Bug Fixes
v8.0.3Compare Source
v8.0.2Compare Source
Renovate configuration
📅 Schedule: "" in timezone America/Los_Angeles.
🚦 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 WhiteSource Renovate. View repository job log here.