Use Node 21 and fix vulnerabilities#2487
Merged
DmitriyKirakosyan merged 1 commit intomasterfrom Apr 15, 2024
Merged
Conversation
AnatolyPristensky
approved these changes
Mar 25, 2024
lucen-ms
approved these changes
Mar 25, 2024
DmitriyKirakosyan
force-pushed
the
use-node21
branch
from
7d3982a to
63885bf
Compare
Merged
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.
This PR includes:
npm audit fix --forceRunning audit fix with --force is ok, as there are only minor version changes. It requires force, because we specified strict versions for the affected packages.