fix: addrssing the vulnerability that came through where jsonwebtoken… #93
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
jkalandaibm
force-pushed
the
jsonwebtoken-alert-fix
branch
from
175c464 to
a17a648
Compare
added 3 commits
December 28, 2022 19:46
… neeeds to be upgraded dependency: none Signed-off-by: Joseph Kalandarishvili <[email protected]>
… neeeds to be upgraded dependency: none Signed-off-by: Joseph Kalandarishvili <[email protected]>
… neeeds to be upgraded Signed-off-by: Joseph Kalandarishvili <[email protected]>
jkalandaibm
force-pushed
the
jsonwebtoken-alert-fix
branch
from
a17a648 to
7e29afd
Compare
kennburger
approved these changes
Jan 3, 2023
Member
|
🎉 This PR is included in version 0.27.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
… needs to be upgraded
dependency: none
PR summary
the following problem was detected in our weekly scans.
As a result, I've tweaked the package-lock.json file to bump the version numbers.
Fixes: https://github.com/IBM/networking-node-sdk/security/dependabot/36
PR Checklist
Please make sure that your PR fulfills the following requirements:
PR Type
What is the current behavior?
Vulnerability scan is generating an alert suggesting a dependency package called jsonwebtoken needs to be updated from version
What is the new behavior?
Vulnerability scan should be updated from 8.5.1 to 9.0.0
Does this PR introduce a breaking change?
Other information