[codex] Update Discord dependencies for security fixes - #2
Draft
gustavByte wants to merge 1 commit into
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
discord.js was updated a little, from ^12.3.1 to ^12.5.3, and package-lock.json was refreshed too. This also pulled some underlying packages to safer versions, especially node-fetch to 2.7.0 and ws to 7.5.10.
GitHub showed two high security alerts in packages the bot uses indirectly. To keep the change small, no big jump to discord.js 14 was done. Instead, the update stays on the latest version in the 12.x line.
Everything was also checked after the change:
npm audit now shows 0 vulnerabilities
node --check index.js passed fine