fix: upgrade vulnerable dependencies for v6.6.0 #448
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
- Upgrade form-data from 4.0.0 to 4.0.4 to fix SNYK-JS-FORMDATA-10841150 (Critical) - Upgrade njwt from 1.0.0 to 2.0.1 to fix SNYK-JS-NJWT-6861582 (High) - Both upgrades are backward compatible with no breaking changes - All tests pass successfully after upgrades
Author
|
@robbat2 You're right, closing this now, thank you ! |
Author
|
@robbat2 On a second look (this PR is months old now 😅 ), yes that commits exist, but only that would only fix the vulnerabilities in |
mrjono1
approved these changes
Nov 19, 2025
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The current v6.6.0 release has two security vulnerabilities:
Issue Number: N/A
What is the new behavior?
This PR upgrades the vulnerable dependencies to their secure versions:
All tests pass successfully after the upgrades.
Does this PR introduce a breaking change?
Other information
Reviewers
@okta/okta-sdk-nodejs-maintainers