chore(packages): update packages with critical and high vulnerabilities #1689
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
- update all packages with critical and high vulnerability level - add package enteries into resolution block in package.json
- update all packages with critical and high vulnerability level - add package enteries into resolution block in package.json
…ols/nodejs into chore/update-packages
1 task
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.
Summary
Some npm package dependencies were raised by Github security advisory to have high and critical security vulnerability levels.
In response to this, I was tasked with updating the package dependencies to a version that has a fix (patch) for the vulnerability.
Description
I updated all package dependencies with critical and high vulnerability level by adding package dependencies and corresponding patch versions into the package.json resolution block.
Note
This should be tested thoroughly to ensure no breaking changes will arise due updated package dependencies
Todo
Typelabel for the PR