Bump axios to 0.31.1#494
Merged
Merged
Conversation
Coverage Report for CI Build 0Coverage decreased (-1.0%) to 81.762%Details
Uncovered ChangesNo uncovered changes found. Coverage Regressions11 previously-covered lines in 2 files lost coverage.
Coverage Stats
💛 - Coveralls |
Add newline at the end of package.json
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
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.
What kind of change does this PR introduce?
Fixes a security vulnerability in axios package listed here: https://github.com/axios/axios/releases/tag/v0.30.3
Did you add tests for your changes?
No (I don't think its relevant for upgrading a dependency
If relevant, link to documentation update:
N/A
Summary
Upgrades Axios to 3.30.3 - addresses a a high-priority vulnerability involving prototype pollution that could lead to a Denial of Service (DoS).
Does this PR introduce a breaking change?
Potentially if the package was using the merging of the proto key with config objects, but I don't believe it to be the case.