bump node-fetch #4807
Closed
bump node-fetch #4807
Conversation
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
Member
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Please describe the changes this PR makes and why it should be merged:
Earlier today an advisory was made for node-fetch. While not being a big issue seeing a
found 1 low severity vulnerabilitydoes not look the greatest. https://www.npmjs.com/advisories/1556Status
Code changes have been tested against the Discord API, or there are no code changes
I know how to update typings and have done so, or typings don't need updating
No code changes were made
No typings needed updating
Semantic versioning classification:
This PR changes the library's interface (methods or parameters added)
This PR only includes non-code changes, like changes to documentation, README, etc.